bgpreport

Network · data from 2026-11-12

AS38611 Bendigo Telco

Registry name: BENDIGOTELCO-AS-AP - Bendigo Community Telco, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38611, 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.
210.9.194.0/23 No ROA Other IRR onlyRADB 670 100% 67
203.29.191.0/24 No ROA Other IRR onlyRADB 168 25% 51
203.193.192.0/19 Valid RIR databaseAPNIC, RADB 673 100% 67
203.193.208.0/21 Valid RIR databaseAPNIC, RADB 673 100% 67
203.193.216.0/21 Valid RIR databaseAPNIC, RADB 673 100% 67
103.12.201.0/24 Valid RIR databaseAPNIC 671 100% 67
103.12.202.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.253.64.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
103.253.64.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
103.253.66.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
113.11.184.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
113.11.184.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
113.11.186.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
180.92.208.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
203.17.148.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
203.17.148.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
203.17.150.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
203.33.236.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
203.55.188.0/24 Valid RIR databaseAPNIC 671 100% 67
203.57.15.0/24 Valid RIR databaseAPNIC 671 100% 67
203.80.168.0/24 Valid RIR databaseAPNIC 671 100% 67
203.193.196.0/22 Valid RIR databaseAPNIC, RADB 671 100% 67
203.193.200.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67
203.193.206.0/23 Valid RIR databaseAPNIC, RADB 671 100% 67

AS-SET

AS38611'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 25 are in fix.csv.

  • ROA: none2
  • Route object: RIR2
  • Route object: not announced21
ChangePrefix or setDetailFull-table peers
ROA: none210.9.194.0/23No ROA covers it. Add a ROA for AS38611, maxLength 23.670 of 673
Route object: RIR210.9.194.0/23Route object only in RADB. Add it in the RIR database for the space.670 of 673
ROA: none203.29.191.0/24No ROA covers it. Add a ROA for AS38611, maxLength 24.168 of 673
Route object: RIR203.29.191.0/24Route object only in RADB. Add it in the RIR database for the space.168 of 673

Route objects not announced

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

103.12.200.0/22APNIC, RADBValid
103.12.200.0/23APNIC, RADBValid
103.12.200.0/24APNICValid
103.12.202.0/24APNICValid
103.12.203.0/24APNICValid
103.211.240.0/22RADBNo ROA
202.0.90.0/24RADBNo ROA
202.124.32.0/20RADBNo ROA
203.16.224.0/24RADBNo ROA
203.16.225.0/24RADBNo ROA
203.27.93.0/24RADBNo ROA
203.33.102.0/24RADBNo ROA
203.34.12.0/23RADBNo ROA
203.34.12.0/24RADBNo ROA
203.34.13.0/24RADBNo ROA
203.63.212.8/29RADBNo ROA
210.8.93.64/27RADBNo ROA
210.8.245.220/30RADBNo ROA
210.9.11.28/30RADBNo ROA
210.9.11.208/28RADBNo ROA
210.9.238.0/24RADBNo 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.