Skip to main content

AS9226

SGIX-AS-AP

1-Net Singapore Pte Ltd

Registry

Authoritative registration data

AS number
9226
Name
SGIX-AS-AP
Organisation
1-Net Singapore Pte Ltd
Country
Flag of Singapore SG Singapore
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

5

IPv6 prefixes

1

Total announced

6

Announced prefixes

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

Prefixes announced by AS9226
202.172.160.0/19 IPv4 /19 not checked
202.172.224.0/19 IPv4 /19 not checked
203.112.160.0/19 IPv4 /19 not checked
202.172.192.0/20 IPv4 /20 not checked
202.172.216.0/21 IPv4 /21 not checked
2402:2400::/33 IPv6 /33 RPKI not found

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 AS9226
Address families
SGIX: Peering LAN 1,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 AS9226 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS9226 in AS paths

Observed upstreams
Families
AS4657 STARHUB-INTERNET 359 1,097
v4 v6
AS7473 SINGTEL-AS-AP 242 785
v4 v6
AS6939 HURRICANE 26 119
v4
AS9304 HUTCHISON-AS-AP 1 5
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS9226 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

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.