Skip to main content

AS201445

Zerval-Network

servperso:upstream:LYG-515436

Registry

Authoritative registration data

AS number
201445
Name
Zerval-Network
Organisation
servperso:upstream:LYG-515436
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

7

Total announced

9

Announced prefixes

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

Prefixes announced by AS201445
44.30.215.0/24 IPv4 /24 not checked
44.30.216.0/24 IPv4 /24 not checked
2a0f:6284:3400::/40 IPv6 /40 RPKI valid
2a0f:6284:3440::/44 IPv6 /44 not checked
2a0b:4e07:26::/48 IPv6 /48 not checked
2a0b:4e07:27::/48 IPv6 /48 not checked
2a0f:6284:341b::/48 IPv6 /48 not checked
2a0f:6284:3467::/48 IPv6 /48 RPKI valid
2a0f:6284:3469::/48 IPv6 /48 RPKI valid

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 AS201445
Address families
LOCIX DUSSELDORF: Peering LAN 10,000 Mbps IPv4 · IPv6
LOCIX FRANKFURT: Peering LAN 10,000 Mbps IPv4 · 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 AS201445 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS201445 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 173 1,711
v6
AS212895 ROUTE64_ORG 149 505
v4 v6
AS41051 FREETRANSIT 67 410
v4 v6
AS214915 PawHost 118 392
v4 v6
AS11967 HOP179 18 130
v6
AS25091 IP-Max 5 59
v4 v6
AS401753 BIXCE 1 9
v4 v6
AS48646 STEFAN6 1 7
v6
AS34927 iFog-GmbH 2 4
v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS201445 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

13 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.