Skip to main content

AS31078

NETWORKTOWN-AS

---------------------------------------------------

Registry

Authoritative registration data

AS number
31078
Name
NETWORKTOWN-AS
Organisation
---------------------------------------------------
Country
RIR
RIPE
Registered
Source:asn:rdap retrieved

IPv4 prefixes

3

IPv6 prefixes

1

Total announced

4

Announced prefixes

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

Prefixes announced by AS31078
217.115.0.0/20 IPv4 /20 not checked
31.220.136.0/21 IPv4 /21 not checked
193.34.24.0/22 IPv4 /22 not checked
2a00:1328::/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 AS31078
Address families
BCIX: BCIX Peering LAN 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 AS31078 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

10 networks seen before AS31078 in AS paths

Observed upstreams
Families
AS13237 LAMBDANET-AS 1,258 2,305
v4 v6
AS9136 1,177 2,037
v4 v6
AS6939 HURRICANE 467 665
v4 v6
AS8218 NEO-ASN 41 158
v4 v6
AS9002 RETN-AS 42 77
v6
AS13030 INIT7 15 67
v4 v6
AS39351 ESAB-AS 17 32
v4 v6
AS24961 16 30
v4 v6
AS6797 8 30
v4 v6
AS20562 7 13
v4 v6

No rows match “”.

Showing of

Observed downstreams

6 networks seen after AS31078 in AS paths

Observed downstreams
Families
AS206028 853 1,408
v4 v6
AS208262 947 1,399
v4 v6
AS50575 425 704
v4 v6
AS208477 283 356
v4
AS31010 110 181
v4 v6
AS211752 11 22
v4 v6

No rows match “”.

Showing of

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 8 75
v4 v6

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.