Skip to main content

AS207306

EVERIANET

Everia Oy

Registry

Authoritative registration data

AS number
207306
Name
EVERIANET
Organisation
Everia Oy
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

2

Total announced

2

Announced prefixes

Observed in BGP by route collectors, not a registry allocation list

Prefixes announced by AS207306
2a0c:b641:640::/48 IPv6 /48 not checked
2a0c:b641:641::/48 IPv6 /48 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

Internet Exchange memberships listed for AS207306
Address families
LOCIX DUSSELDORF: Peering LAN 1,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 1,000 Mbps IPv4 · IPv6
ixFabric - Amsterdam 1,000 Mbps IPv6
ixFabric - Dusseldorf 1,000 Mbps IPv6
ixFabric - London 1,000 Mbps IPv6

No rows match “”.

Showing – of

Source:peeringdb retrieved

Exchange membership means the network has a listed connection; it does not prove peering with other members.

Observed adjacencies

Networks seen next to AS207306 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

6 networks seen before AS207306 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 188 274
v6
AS34872 Servperso_Systems 46 61
v6
AS25091 IP-Max 3 5
v6
AS34927 iFog-GmbH 2 2
v6
AS48646 STEFAN6 1 1
v6
AS401753 BIXCE 1 1
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS207306 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

10 adjacencies that may be an artefact of collector peering

No rows match “”.

Showing – of

Note:
These are observed adjacencies derived from BGP path data, not confirmed commercial relationships. A network appearing before another in an AS path does not establish that it is a paying transit customer, a settlement free peer, or anything else contractual. Adjacencies marked uncertain were seen only as direct peers of a route collector, so the collector's own peering may have created them.