Skip to main content

AS209552

Jan

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

Registry

Authoritative registration data

AS number
209552
Name
Jan
Organisation
--------------------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

0

IPv6 prefixes

7

Total announced

7

Announced prefixes

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

Prefixes announced by AS209552
2a06:de01:c0::/44 IPv6 /44 not checked
2602:f9ba:b3::/48 IPv6 /48 not checked
2a06:de01:c1::/48 IPv6 /48 not checked
2a06:de01:c2::/48 IPv6 /48 not checked
2a0b:4e07:2d::/48 IPv6 /48 not checked
2a0f:85c1:51::/48 IPv6 /48 not checked
2a13:9500:48::/48 IPv6 /48 not checked

No rows match “”.

Showing of

Source:ripestat:announced-prefixes observed

Observed adjacencies

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

Source:ripestat:asn-neighbours observed

Observed upstreams

11 networks seen before AS209552 in AS paths

Observed upstreams
Families
AS6939 191 992
v6
AS214757 217 909
v6
AS215638 68 280
v6
AS393577 57 194
v6
AS41051 43 57
v6
AS8218 4 37
v6
AS39351 2 6
v6
AS49434 2 5
v6
AS56655 1 4
v6
AS60171 1 4
v6
AS50673 2 2
v6

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS209552 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

Uncertain adjacencies
Families
AS24482 1 21
v6
AS203472 1 9
v6
AS47692 1 8
v6
AS215628 1 7
v6
AS28910 1 4
v6
AS41327 1 4
v6
AS48919 1 4
v6
AS199524 1 4
v6
AS205112 1 4
v6
AS208972 1 4
v6
AS209823 1 4
v6
AS3170 1 3
v6
AS50629 1 3
v6

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.