bgpreport

Network · data from 2026-11-12

AS20460 MYTHOSTECH - TFB NET

Registry name: MYTHOSTECH - TFB NET, US · not in PeeringDB

8IPv4 routes 37.5% RPKI valid · 12.5% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
5No ROA 7 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS20460, seen from no peer

Announced routes

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

72.14.128.0/24 No ROA None 672 100% 67
72.14.131.0/24 No ROA None 672 100% 67
72.14.140.0/24 No ROA None 672 100% 67
72.14.158.0/24 No ROA None 672 100% 67
72.14.159.0/24 No ROA None 672 100% 67
72.14.129.0/24 Valid None 672 100% 67
72.14.150.0/24 Valid None 672 100% 67
72.14.156.0/24 Valid Other IRR onlyRADB 672 100% 67

AS-SET

AS20460 isn't in PeeringDB, where networks name their 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 18 are in fix.csv.

  • ROA: none5
  • Route object: none7
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none72.14.128.0/24No ROA covers it. Add a ROA for AS20460, maxLength 24.672 of 673
Route object: none72.14.128.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
ROA: none72.14.131.0/24No ROA covers it. Add a ROA for AS20460, maxLength 24.672 of 673
Route object: none72.14.131.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
ROA: none72.14.140.0/24No ROA covers it. Add a ROA for AS20460, maxLength 24.672 of 673
Route object: none72.14.140.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
ROA: none72.14.158.0/24No ROA covers it. Add a ROA for AS20460, maxLength 24.672 of 673
Route object: none72.14.158.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
ROA: none72.14.159.0/24No ROA covers it. Add a ROA for AS20460, maxLength 24.672 of 673
Route object: none72.14.159.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
Route object: none72.14.129.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
Route object: none72.14.150.0/24No route object for it. Add a route object with origin AS20460 in the RIR database for the space.672 of 673
Route object: RIR72.14.156.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 AS20460 whose prefix no peer sees AS20460 announce. Many are kept on purpose (backup routes, space announced only in some places).

204.212.132.0/24RADBNo ROA
204.216.232.0/22RADBNo ROA
209.68.228.0/23RADBNo ROA
216.120.16.0/23RADBNo ROA
216.120.120.0/22RADBNo 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.