Skip to main content

AS22549

TBDSL-01

KUDUCOM

Registry

Authoritative registration data

AS number
22549
Name
TBDSL-01
Organisation
KUDUCOM
Country
—
RIR
ARIN
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

3

Total announced

8

Announced prefixes

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

Prefixes announced by AS22549
209.216.64.0/19 IPv4 /19 not checked
63.135.224.0/20 IPv4 /20 not checked
68.65.16.0/20 IPv4 /20 not checked
68.65.28.0/22 IPv4 /22 not checked
68.65.23.0/24 IPv4 /24 not checked
2604:a440:1::/48 IPv6 /48 not checked
2604:a440:fffe::/48 IPv6 /48 not checked
2604:a440:ffff::/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 AS22549
Address families
Digital Realty Atlanta 10,000 Mbps IPv4 · IPv6
TPAIX 1,000 Mbps IPv4

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 AS22549 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

3 networks seen before AS22549 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 2,352 35,958
v4 v6
AS174 COGENT-174 348 2,755
v4 v6
AS3257 GTT-BACKBONE 42 333
v4

No rows match “”.

Showing – of

Observed downstreams

2 networks seen after AS22549 in AS paths

Observed downstreams
Families
AS394896 AHL-759-394896 1,540 23,932
v4 v6
AS398779 ACEHOST 673 12,606
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS49544 i3Dnet 10 254
v4 v6
AS1828 UNITAS 10 127
v4 v6
AS19151 BBO-1 4 80
v4

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.