bgpreport

Network · data from 2026-11-12

AS133045 NSW Electricity

Registry name: NSW-ENO-AS-AP - NSW Electricity Networks Operations Pty Limited, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS133045, 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.

103.75.4.0/22 No ROA RIR databaseAPNIC, RADB 668 99% 67
103.75.6.0/23 No ROA RIR databaseAPNIC 668 99% 67
137.59.72.0/22 No ROA RIR databaseAPNIC, RADB 668 99% 67
137.59.72.0/23 No ROA RIR databaseAPNIC 668 99% 67
2407:3a80::/32 No ROA RIR databaseAPNIC, RADB 636 100% 69
148.195.20.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
148.195.28.0/22 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
148.195.135.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
148.195.143.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
148.195.145.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67
148.195.230.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 668 99% 67

AS-SET

PeeringDB's irr_as_set for AS133045: AS-133045-TRANSIT. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS133045 isn't in the set, or no route object for AS133045 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS133045 in itNot covered
AS-133045-TRANSIT APNIC 71181 Yes 0

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 36 are in fix.csv.

  • ROA: none5
  • Route object: not announced31
ChangePrefix or setDetailFull-table peers
ROA: none103.75.4.0/22No ROA covers it. Add a ROA for AS133045, maxLength 22.668 of 673
ROA: none103.75.6.0/23No ROA covers it. Add a ROA for AS133045, maxLength 23.668 of 673
ROA: none137.59.72.0/22No ROA covers it. Add a ROA for AS133045, maxLength 22.668 of 673
ROA: none137.59.72.0/23No ROA covers it. Add a ROA for AS133045, maxLength 23.668 of 673
ROA: none2407:3a80::/32No ROA covers it. Add a ROA for AS133045, maxLength 32.636 of 636

Route objects not announced

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

103.75.4.0/23APNICNo ROA
103.75.4.0/24APNICNo ROA
103.75.5.0/24APNICNo ROA
103.75.6.0/24APNICNo ROA
103.75.7.0/24APNICNo ROA
137.59.72.0/24APNICNo ROA
137.59.73.0/24APNICNo ROA
137.59.74.0/23APNICNo ROA
137.59.74.0/24APNICNo ROA
137.59.75.0/24APNICNo ROA
148.195.18.0/23RADBNo ROA
148.195.18.0/24APNICValid
148.195.20.0/23APNICValid
148.195.20.0/24APNICValid
148.195.21.0/24APNICValid
148.195.22.0/23APNICValid
148.195.22.0/24APNICValid
148.195.23.0/24APNICValid
148.195.28.0/23APNICValid
148.195.28.0/24APNICValid
148.195.29.0/24APNICValid
148.195.30.0/23APNICValid
148.195.30.0/24APNICValid
148.195.31.0/24APNICValid
159.73.0.0/16APNICValid
2407:3a80::/33APNICNo ROA
2407:3a80::/34APNICNo ROA
2407:3a80:4000::/34APNICNo ROA
2407:3a80:8000::/33APNICNo ROA
2407:3a80:8000::/34APNICNo ROA
2407:3a80:c000::/34APNICNo 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.