Skip to main content

AS8100

SPLICE-AS-AP

Splice Internet

Registry

Authoritative registration data

AS number
8100
Name
SPLICE-AS-AP
Organisation
Splice Internet
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

1

Total announced

5

Announced prefixes

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

Prefixes announced by AS8100
157.85.128.0/18 IPv4 /18 not checked
163.128.244.0/23 IPv4 /23 not checked
157.85.128.0/24 IPv4 /24 not checked
157.85.129.0/24 IPv4 /24 not checked
2402:58a0::/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 AS8100
Address families
EdgeIX - Melbourne: Main 10,000 Mbps IPv4 · IPv6
IX Australia Melbourne (VIC-IX): VIC-IX 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 AS8100 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

2 networks seen before AS8100 in AS paths

Observed upstreams
Families
AS137409 GSLNETWORKS-AS-AP 154 807
v4 v6
AS6939 HURRICANE 32 77
v4 v6

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS8100 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

1 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS35280 F5 1 4
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.