Skip to main content

AS151404

THREEGOTECHNOLOGY-AS-AP

3GO TECHNOLOGY PTE. LTD.

Registry

Authoritative registration data

AS number
151404
Name
THREEGOTECHNOLOGY-AS-AP
Organisation
3GO TECHNOLOGY PTE. LTD.
Country
Flag of Singapore SG Singapore
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

1

IPv6 prefixes

1

Total announced

2

Announced prefixes

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

Prefixes announced by AS151404
103.253.229.0/24 IPv4 /24 not checked
2001:df3:1840::/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

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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

Source:ripestat:asn-neighbours observed

Observed upstreams

5 networks seen before AS151404 in AS paths

Observed upstreams
Families
AS58453 CMI-INT-HK 1,636 4,431
v4 v6
AS17497 LGHL-AS-AP 472 949
v4 v6
AS6939 HURRICANE 76 107
v4 v6
AS151552 IDNIC-THREEGOTECHNOLOGY-AS-ID 7 14
v4
AS9304 HUTCHISON-AS-AP 2 3
v4

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS151404 in AS paths

Observed downstreams
Families
AS151552 IDNIC-THREEGOTECHNOLOGY-AS-ID 1,377 4,008
v4 v6
AS141356 UAL-AS-AP 272 679
v4
AS134474 MCTPL-AS-AP 125 166
v4

No rows match “”.

Showing – of

Uncertain adjacencies

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