Skip to main content

AS37904

BBIX-NETWORK

BBIX, Inc.

Registry

Authoritative registration data

AS number
37904
Name
BBIX-NETWORK
Organisation
BBIX, Inc.
Country
Flag of Japan JP Japan
RIR
APNIC
Registered
—
Source:asn:rdap retrieved

IPv4 prefixes

2

IPv6 prefixes

1

Total announced

3

Announced prefixes

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

Prefixes announced by AS37904
218.231.244.0/23 IPv4 /23 not checked
218.231.248.0/23 IPv4 /23 not checked
2403:c780:7201::/48 IPv6 /48 RPKI valid

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 AS37904
Address families
BBIX Hong Kong 100,000 Mbps IPv4 · IPv6
BBIX Manila 800,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 AS37904 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

1 networks seen before AS37904 in AS paths

Observed upstreams
Families
AS63927 RISE-HK 1,063 2,832
v4 v6

No rows match “”.

Showing – of

Observed downstreams

3 networks seen after AS37904 in AS paths

Observed downstreams
Families
AS135607 INFINIVAN-AS-AP 64 786
v4
AS14789 CLOUDFLARENET 332 590
v4 v6
AS20940 AKAMAI-ASN1 332 581
v4 v6

No rows match “”.

Showing – of

Uncertain adjacencies

3 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS17639 CONVERGE-AS 1 3
v4 v6
AS24482 SGGS-AS-AP 1 3
v4 v6
AS142271 DOUBLESQUARE-AS-AP 1 1
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.