bgpreport

Network · data from 2026-11-12

AS32000 AS32000 - Tnet Broadband Internet

Registry name: AS32000 - Tnet Broadband Internet, US · not in PeeringDB

4IPv4 routes 75.0% RPKI valid · 50.0% with a route object
0IPv6 routes
0RPKI invalid 0 origin · 0 maxLength
1No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS32000, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS32000, 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.
55.23.0.0/16 No ROA None 670 100% 67
148.59.246.0/24 Valid Nonecovered by 148.59.246.0/23 673 100% 67
23.159.184.0/24 Valid RIR databaseARIN, RADB 671 100% 67
148.59.244.0/22 Valid RIR databaseARIN, RADB 671 100% 68

AS-SET

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

  • ROA: none1
  • Route object: none2
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: none55.23.0.0/16No ROA covers it. Add a ROA for AS32000, maxLength 16.670 of 673
Route object: none55.23.0.0/16No route object for it. Add a route object with origin AS32000 in the RIR database for the space.670 of 673
Route object: none148.59.246.0/24No route object for it. A route object for 148.59.246.0/23 with origin AS32000 covers it (filters allowing more-specifics accept it). Add a route object with origin AS32000 in the RIR database for the space.673 of 673

Route objects not announced

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

148.59.244.0/23RADBValid
148.59.246.0/23RADBValid
2607:31c0::/32ARINValid

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.