Skip to main content

AS47689

Pudu

Main public network

Registry

Authoritative registration data

AS number
47689
Name
Pudu
Organisation
Main public network
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

8

Total announced

13

Announced prefixes

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

Prefixes announced by AS47689
23.144.196.0/24 IPv4 /24 not checked
44.31.59.0/24 IPv4 /24 not checked
64.187.208.0/24 IPv4 /24 not checked
64.187.209.0/24 IPv4 /24 not checked
91.193.114.0/24 IPv4 /24 not checked
2a06:a340::/32 IPv6 /32 not checked
2602:f57d::/40 IPv6 /40 not checked
2001:67c:81c::/48 IPv6 /48 not checked
2001:67c:b90::/48 IPv6 /48 not checked
2a06:a005:a19::/48 IPv6 /48 not checked
2a06:a341::/48 IPv6 /48 not checked
2a06:a341:c0fe::/48 IPv6 /48 not checked
2a07:54c1:41ee::/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 AS47689
Address families
AMS-IX 1,000 Mbps IPv4 · IPv6
F4IX MCI 1,000 Mbps IPv4 · IPv6
FogIXP 1,000 Mbps IPv4 · IPv6
FogIXP Frankfurt 10,000 Mbps IPv4 · IPv6
KleyReX: Peering LAN 100 Mbps IPv4 · IPv6
MICE: Shared Peering 10,000 Mbps IPv4 · IPv6
NL-ix: Main 100 Mbps IPv4 · IPv6
SIX Seattle (Jumbo): MTU 9000 11,000 Mbps IPv4 · IPv6
SIX Seattle: MTU 1500 11,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 AS47689 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

45 networks seen before AS47689 in AS paths

No rows match “”.

Showing of

Observed downstreams

1 networks seen after AS47689 in AS paths

Observed downstreams
Families
AS210761 PuduTest 238 345
v6

No rows match “”.

Showing of

Uncertain adjacencies

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