bgpreport

Network · data from 2026-11-12

AS58580 Fastrack Technology

Registry name: Fastrack - Fastrack Technology, AU · PeeringDB

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

Announced routes

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

2406:1f00::/48 No ROA Nonecovered by 2406:1f00::/32 635 100% 67
2406:1f00:1::/48 No ROA Nonecovered by 2406:1f00::/32 631 99% 69
185.254.56.0/23 Valid Nonecovered by 185.254.56.0/22 671 100% 68
168.245.200.0/23 Valid None 658 98% 67
199.101.108.0/23 Valid None 658 98% 67
103.8.29.0/24 Valid Other IRR onlyRADB 672 100% 67
103.18.84.0/23 Valid Other IRR onlyRADB 672 100% 67
103.18.86.0/24 Valid Other IRR onlyRADB 672 100% 67
103.18.84.0/24 Valid Other IRR onlyRADB 671 100% 67
103.18.87.0/24 Valid Other IRR onlyRADB 671 100% 67
103.245.220.0/23 Valid Other IRR onlyRADB 671 100% 67
103.245.220.0/24 Valid Other IRR onlyRADB 671 100% 67
103.245.221.0/24 Valid Other IRR onlyRADB 671 100% 67
163.47.101.0/24 Valid Other IRR onlyRADB 671 100% 69
163.47.102.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 67
163.47.103.0/24 Valid Other IRR onlyNTTCOM, RADB 671 100% 69
103.8.28.0/24 Valid Other IRR onlyRADB 670 100% 68
163.47.100.0/24 Valid Other IRR onlyRADB 669 99% 69
168.245.202.0/24 Valid Other IRR onlyALTDB 669 99% 69
168.245.203.0/24 Valid Other IRR onlyALTDB 669 99% 69
199.101.110.0/24 Valid Other IRR onlyALTDB 669 99% 69
199.101.111.0/24 Valid Other IRR onlyALTDB 669 99% 69
103.152.3.0/24 Valid RIR databaseAPNIC, RADB 673 100% 67
103.177.46.0/23 Valid RIR databaseAPNIC 673 100% 67
103.186.82.0/24 Valid RIR databaseAPNIC 671 100% 68
185.254.56.0/22 Valid RIR databaseRIPE 671 100% 68
185.254.56.0/24 Valid RIR databaseRIPE 671 100% 68
103.152.2.0/24 Valid RIR databaseAPNIC 670 100% 68
103.186.83.0/24 Valid RIR databaseAPNIC 670 100% 67
185.254.57.0/24 Valid RIR databaseRIPE 670 100% 68
185.254.58.0/24 Valid RIR databaseRIPE 670 100% 68
185.254.59.0/24 Valid RIR databaseRIPE 670 100% 68

AS-SET

AS58580'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 53 are in fix.csv.

  • ROA: none2
  • Route object: none5
  • Route object: RIR17
  • Route object: not announced29
ChangePrefix or setDetailFull-table peers
ROA: none2406:1f00::/48No ROA covers it. Add a ROA for AS58580, maxLength 48.635 of 636
Route object: none2406:1f00::/48No route object for it. A route object for 2406:1f00::/32 with origin AS58580 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58580 in the RIR database for the space.635 of 636
ROA: none2406:1f00:1::/48No ROA covers it. Add a ROA for AS58580, maxLength 48.631 of 636
Route object: none2406:1f00:1::/48No route object for it. A route object for 2406:1f00::/32 with origin AS58580 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58580 in the RIR database for the space.631 of 636
Route object: none185.254.56.0/23No route object for it. A route object for 185.254.56.0/22 with origin AS58580 covers it (filters allowing more-specifics accept it). Add a route object with origin AS58580 in the RIR database for the space.671 of 673
Route object: none168.245.200.0/23No route object for it. Add a route object with origin AS58580 in the RIR database for the space.658 of 673
Route object: none199.101.108.0/23No route object for it. Add a route object with origin AS58580 in the RIR database for the space.658 of 673
Route object: RIR103.8.29.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.18.84.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.18.86.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR103.18.84.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.18.87.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.245.220.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.245.220.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.245.221.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR163.47.101.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR163.47.102.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR163.47.103.0/24Route object only in NTTCOM, RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR103.8.28.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR163.47.100.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR168.245.202.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR168.245.203.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR199.101.110.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673
Route object: RIR199.101.111.0/24Route object only in ALTDB. Add it in the RIR database for the space.669 of 673

Route objects not announced

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

103.8.28.0/23APNICValid
103.18.84.0/22RADBValid
103.18.85.0/24RADBValid
103.18.86.0/23RADBValid
103.54.232.0/22APNICValid
103.54.232.0/23APNICValid
103.54.232.0/24APNICValid
103.54.233.0/24APNICValid
103.54.234.0/23APNICValid
103.54.234.0/24APNICValid
103.54.235.0/24APNICValid
103.62.36.0/22APNIC, NTTCOMValid
103.62.36.0/23APNIC, NTTCOM, RADBValid
103.62.36.0/24APNIC, RADBValid
103.62.37.0/24APNIC, RADBValid
103.62.38.0/23APNIC, NTTCOMValid
103.62.38.0/24APNIC, RADBValid
103.62.39.0/24APNIC, NTTCOM, RADBValid
103.129.156.0/22RADBNo ROA
103.152.2.0/23APNICValid
103.177.46.0/24APNICValid
103.177.47.0/24APNICValid
103.186.82.0/23APNICValid
118.127.160.0/19RADBNo ROA
163.47.100.0/22RADBValid
163.47.100.0/23RADBValid
163.47.102.0/23NTTCOM, RADBValid
2001:470:155::/48ARINValid
2406:1f00::/32NTTCOMNo 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.