bgpreport

Network · data from 2026-11-12

AS38456 SpeedCast Australia

Registry name: SPEEDCAST-AU - SPEEDCAST AUSTRALIA PTY LIMITED, AU · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS38456, 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.212.40.0/24 No ROA Other IRR onlyRADB 672 100% 67
103.11.160.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.11.161.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.11.162.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.11.163.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.249.49.0/24 Valid RIR databaseAPNIC 672 100% 67
103.249.50.0/24 Valid RIR databaseAPNIC 672 100% 67
103.249.51.0/24 Valid RIR databaseAPNIC 672 100% 67
110.232.148.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
110.232.150.0/24 Valid RIR databaseAPNIC 672 100% 67
110.232.151.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
111.92.177.0/24 Valid RIR databaseAPNIC 672 100% 67
111.92.179.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
122.200.58.0/24 Valid RIR databaseAPNIC 672 100% 67
122.200.59.0/24 Valid RIR databaseAPNIC, NTTCOM, RADB 672 100% 67
122.200.60.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
182.236.116.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
182.236.117.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.245.108.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.245.109.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.245.110.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
192.245.112.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.162.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.163.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.164.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.168.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.169.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
202.5.177.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
203.86.208.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.209.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.210.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.211.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.212.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.213.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.214.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.215.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.219.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.220.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.221.0/24 Valid RIR databaseAPNIC 672 100% 67
203.86.222.0/24 Valid RIR databaseAPNIC 672 100% 67

AS-SET

AS38456'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 59 are in fix.csv.

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced57
ChangePrefix or setDetailFull-table peers
ROA: none103.212.40.0/24No ROA covers it. Add a ROA for AS38456, maxLength 24.672 of 673
Route object: RIR103.212.40.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

27.122.0.0/22RADBNo ROA
43.245.212.0/22RADBNo ROA
43.245.215.0/24RADBNo ROA
103.9.142.0/24RADBNo ROA
103.9.143.0/24RADBNo ROA
103.11.160.0/22RADBNo ROA
103.11.162.0/23RADBNo ROA
103.21.248.0/22RADBNo ROA
103.112.101.0/24APNICValid
103.148.4.0/23RADBNo ROA
103.148.4.0/24RADBNo ROA
103.148.5.0/24RADBNo ROA
103.167.47.0/24RADBNo ROA
113.20.32.0/19RADBNo ROA
113.21.96.0/19RADBNo ROA
122.200.58.0/23RADBNo ROA
151.216.33.0/24RADBNo ROA
175.176.148.0/23RADBNo ROA
199.7.82.0/23RADBNo ROA
199.7.83.0/24RADBNo ROA
202.2.96.0/19NTTCOM, RADBNo ROA
202.2.96.0/20NTTCOM, RADBNo ROA
202.2.96.0/21NTTCOM, RADBNo ROA
202.2.96.0/22NTTCOM, RADBNo ROA
202.2.96.0/23NTTCOM, RADBNo ROA
202.2.96.0/24NTTCOMNo ROA
202.2.97.0/24NTTCOM, RADBNo ROA
202.2.98.0/23NTTCOM, RADBNo ROA
202.2.98.0/24NTTCOM, RADBNo ROA
202.2.99.0/24NTTCOM, RADBNo ROA
202.2.100.0/22NTTCOM, RADBNo ROA
202.2.100.0/23NTTCOM, RADBNo ROA
202.2.100.0/24NTTCOMNo ROA
202.2.101.0/24NTTCOM, RADBNo ROA
202.2.102.0/23NTTCOM, RADBNo ROA
202.2.102.0/24NTTCOM, RADBNo ROA
202.2.103.0/24NTTCOM, RADBNo ROA
202.2.104.0/21NTTCOM, RADBNo ROA
202.2.104.0/22NTTCOMNo ROA
202.2.104.0/23NTTCOMNo ROA
202.2.104.0/24NTTCOMNo ROA
202.2.105.0/24NTTCOMNo ROA
202.2.106.0/23NTTCOMNo ROA
202.2.106.0/24NTTCOMNo ROA
202.2.107.0/24NTTCOMNo ROA
202.2.108.0/22NTTCOMNo ROA
202.2.108.0/23NTTCOMNo ROA
202.2.108.0/24NTTCOMNo ROA
202.2.109.0/24NTTCOMNo ROA
202.2.110.0/23NTTCOMNo ROA
202.2.110.0/24NTTCOMNo ROA
202.2.111.0/24NTTCOMNo ROA
202.5.190.0/24APNIC, RADBValid
203.86.208.0/21RADBNo ROA
203.86.220.0/22RADBNo ROA
2406:5e00::/48APNICValid
2406:5e00:1::/48APNICValid

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.