bgpreport

Network · data from 2026-11-12

AS45873 Nehos Communications

Registry name: NEHOS-AU - Nehos Communications Pty Ltd, AU · PeeringDB

3IPv4 routes 100.0% RPKI valid · 100.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 0 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
13Route objects not announced registered with origin AS45873, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS45873, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
180.94.236.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
180.94.236.0/23 Valid RIR databaseAPNIC, RADB 670 100% 67
180.94.237.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
2401:e880::/32 Valid RIR databaseAPNIC, RADB 636 100% 69
2401:e880:5::/48 Valid RIR databaseAPNIC 636 100% 67
2401:e880:4::/48 Valid RIR databaseAPNIC 633 100% 69

AS-SET

AS45873's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 13 are in fix.csv.

  • Route object: not announced13

Route objects not announced

Route objects with origin AS45873 whose prefix no peer sees AS45873 announce. Many are kept on purpose (backup routes, space announced only in some places).

103.100.120.0/24RADBNo ROA
103.100.121.0/24RADBNo ROA
115.165.169.0/24RADBNo ROA
115.165.171.0/24RADBNo ROA
115.165.173.0/24RADBNo ROA
115.165.174.0/24RADBNo ROA
115.165.175.0/24RADBNo ROA
180.94.236.0/22RADBNo ROA
185.111.40.0/22RADBNo ROA
185.207.196.0/22RADBNo ROA
188.209.144.0/21RADBNo ROA
188.209.154.0/23RADBNo ROA
212.95.128.0/19RADBNo ROA

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.