Skip to main content

AS139225

WHATBOX-AS-AP

Whatbox Inc.

Registry

Authoritative registration data

AS number
139225
Name
WHATBOX-AS-AP
Organisation
Whatbox Inc.
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 AS139225
103.140.3.0/24 IPv4 /24 not checked
2001:df0:a280::/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 AS139225
Address families
Equinix Singapore 10,000 Mbps IPv4 · IPv6
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 AS139225 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

9 networks seen before AS139225 in AS paths

Observed upstreams
Families
AS6939 HURRICANE 217 324
v4 v6
AS174 COGENT-174 152 215
v4 v6
AS6453 AS6453 78 111
v4 v6
AS33891 CORE-BACKBONE 5 7
v4
AS9583 SIFY-AS-IN 1 2
v4
AS9304 HUTCHISON-AS-AP 1 1
v4
AS15802 DU-AS1 1 1
v4
AS17557 PKTELECOM-AS-PK 1 1
v4
AS137409 GSLNETWORKS-AS-AP 1 1
v4

No rows match “”.

Showing of

Observed downstreams

0 networks seen after AS139225 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

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