Skip to main content

AS208920

RocketWay-AS

------------------------------------------------------

Registry

Authoritative registration data

AS number
208920
Name
RocketWay-AS
Organisation
------------------------------------------------------
Country
—
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

2

Total announced

6

Announced prefixes

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

Prefixes announced by AS208920
185.126.204.0/22 IPv4 /22 RPKI valid
185.148.116.0/22 IPv4 /22 not checked
45.130.108.0/22 IPv4 /22 RPKI valid
85.116.136.0/22 IPv4 /22 RPKI valid
2a06:c100::/29 IPv6 /29 RPKI valid
2a07:5f00::/29 IPv6 /29 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 AS208920
Address families
Ge-DIX 10,000 Mbps IPv4 · IPv6
MIX-IT 10,000 Mbps IPv4 · IPv6
Namex Rome: VLAN Peering 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 AS208920 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

15 networks seen before AS208920 in AS paths

Observed upstreams
Families
AS5398 InternetONE 223 741
v4 v6
AS20912 ASN-PANSERVICE 168 527
v4 v6
AS6939 HURRICANE 25 101
v4
AS8218 NEO-ASN 7 57
v4 v6
AS5405 INTERDOTLINK 8 45
v4 v6
AS14840 ASN14840 2 20
v4
AS4455 BSO 2 14
v4 v6
AS29075 IELO 3 11
v4 v6
AS24961 MYLOC-AS 2 10
v4 v6
AS31543 MYNET-AS 1 6
v4 v6
AS6204 ZET-NET 1 4
v4
AS22356 ASN22356 1 4
v4
AS60171 AFRIX-AS 1 4
v4
AS137409 GSLNETWORKS-AS-AP 1 4
v4
AS263444 ASN263444 1 4
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS208920 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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