Skip to main content

AS4778

BORAL-LIMITED-AP

Optus Customer Network

Registry

Authoritative registration data

AS number
4778
Name
BORAL-LIMITED-AP
Organisation
Optus Customer Network
Country
Flag of Australia AU Australia
RIR
APNIC
Registered
Source:asn:rdap retrieved

IPv4 prefixes

4

IPv6 prefixes

0

Total announced

4

Announced prefixes

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

Prefixes announced by AS4778
203.20.216.0/24 IPv4 /24 not checked
203.20.217.0/24 IPv4 /24 not checked
203.20.218.0/24 IPv4 /24 not checked
203.20.219.0/24 IPv4 /24 not checked

No rows match “”.

Showing – of

Source:ripestat:announced-prefixes observed

Internet Exchanges

Exchanges where this network has a listed peering LAN connection

No Internet Exchange memberships found

The exchange directory has no current membership records for this AS.

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 AS4778 in BGP paths by route collectors.

Source:ripestat:asn-neighbours observed

Observed upstreams

4 networks seen before AS4778 in AS paths

Observed upstreams
Families
AS49915 MEGAPORT 276 676
v4
AS4826 237 602
v4
AS6939 HURRICANE 28 62
v4
AS64073 1 2
v4

No rows match “”.

Showing – of

Observed downstreams

0 networks seen after AS4778 in AS paths

No downstreams observed

This AS was not seen carrying traffic towards another network.

Uncertain adjacencies

5 adjacencies that may be an artefact of collector peering

Uncertain adjacencies
Families
AS24482 SGGS-AS-AP 1 2
v4
AS35280 F5 1 2
v4
AS36236 NETACTUATE 1 2
v4
AS49544 i3Dnet 1 2
v4
AS132847 1 2
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.