Skip to main content

AS5580

GTT-ASIA

GTT

Registry

Authoritative registration data

AS number
5580
Name
GTT-ASIA
Organisation
GTT
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

35

IPv6 prefixes

2

Total announced

37

Announced prefixes

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

Prefixes announced by AS5580
59.191.240.0/20 IPv4 /20 not checked
103.230.248.0/22 IPv4 /22 not checked
185.162.112.0/22 IPv4 /22 not checked
195.134.216.0/22 IPv4 /22 not checked
195.143.68.0/22 IPv4 /22 not checked
203.95.212.0/22 IPv4 /22 not checked
212.56.20.0/22 IPv4 /22 not checked
64.235.252.0/22 IPv4 /22 not checked
69.31.128.0/22 IPv4 /22 not checked
103.207.156.0/23 IPv4 /23 not checked
103.232.34.0/23 IPv4 /23 not checked
103.47.76.0/23 IPv4 /23 not checked
103.53.152.0/23 IPv4 /23 not checked
64.235.224.0/23 IPv4 /23 not checked
64.235.234.0/23 IPv4 /23 not checked
64.235.238.0/23 IPv4 /23 not checked
64.235.240.0/23 IPv4 /23 not checked
64.235.244.0/23 IPv4 /23 not checked
64.235.250.0/23 IPv4 /23 not checked
69.31.132.0/23 IPv4 /23 not checked
64.235.225.0/24 IPv4 /24 not checked
64.235.227.0/24 IPv4 /24 not checked
64.235.228.0/24 IPv4 /24 not checked
64.235.230.0/24 IPv4 /24 not checked
64.235.232.0/24 IPv4 /24 not checked
64.235.236.0/24 IPv4 /24 not checked
64.235.244.0/24 IPv4 /24 not checked
64.235.245.0/24 IPv4 /24 not checked
64.235.246.0/24 IPv4 /24 not checked
64.235.248.0/24 IPv4 /24 not checked
64.235.249.0/24 IPv4 /24 not checked
69.31.137.0/24 IPv4 /24 not checked
69.31.138.0/24 IPv4 /24 not checked
69.31.139.0/24 IPv4 /24 not checked
69.31.140.0/24 IPv4 /24 not checked
2400:eac0::/32 IPv6 /32 not checked
2400:f780::/32 IPv6 /32 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 AS5580
Address families
Equinix Hong Kong 10,000 Mbps IPv4 · IPv6
Equinix Singapore 100,000 Mbps IPv4 · IPv6
Equinix Tokyo 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 AS5580 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

14 networks seen before AS5580 in AS paths

Observed upstreams
Families
AS3257 GTT-BACKBONE 5,705 21,067
v4 v6
AS3491 PCCWG-APAC-HK 211 2,595
v4 v6
AS6939 HURRICANE 28 808
v4
AS4657 STARHUB-INTERNET 367 698
v4 v6
AS137409 GSLNETWORKS-AS-AP 82 411
v4
AS286 28 148
v4 v6
AS45629 JASTEL-NETWORK-TH-AP 16 43
v6
AS8966 Etisalat-AS 3 39
v4
AS15802 DU-AS1 7 35
v4
AS20485 24 29
v4
AS17557 PKTELECOM-AS-PK 1 28
v4
AS9505 TWGATE-AP 1 27
v4
AS138997 EDCL-AS-AP 3 5
v4
AS38008 2 2
v4

No rows match “”.

Showing of

Observed downstreams

33 networks seen after AS5580 in AS paths

Observed downstreams
Families
AS30058 877 3,513
v4 v6
AS1341 1,033 1,969
v4 v6
AS9829 BSNL-NIB 328 1,479
v4 v6
AS3257 GTT-BACKBONE 343 1,389
v4
AS10806 277 1,339
v4
AS19527 70 782
v4 v6
AS25896 277 671
v4
AS394977 508 667
v4 v6
AS13150 CATON 94 516
v4
AS131189 257 347
v4
AS399678 265 335
v4
AS3291 262 332
v4
AS11941 258 324
v4
AS1678 254 319
v4
AS9229 250 319
v4
AS13464 177 221
v4
AS56077 180 217
v4
AS38195 SUPERLOOP-AS-AP 93 215
v6
AS198651 112 149
v4 v6
AS18723 14 67
v4
AS63399 46 62
v4 v6
AS6404 45 52
v4
AS16740 23 38
v4 v6
AS62713 30 34
v4 v6
AS203256 17 29
v4
AS20077 18 23
v4
AS133052 19 22
v4
AS17060 19 21
v4
AS40934 7 21
v4
AS199569 8 16
v4
AS16645 EPIQSYSTEMS 6 9
v4
AS21509 6 9
v4
AS10780 4 4
v4

No rows match “”.

Showing of

Uncertain adjacencies

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