bgpreport

Network · data from 2026-11-12

AS263302 AS263302 - TORPEDOLINK TELECOM

Registry name: AS263302 - TORPEDOLINK TELECOM, BR · not in PeeringDB

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

Announced routes

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

191.6.248.0/24 Valid Other IRR onlyRADB 672 100% 67
191.6.250.0/24 Valid Other IRR onlyRADB 671 100% 67
191.6.252.0/23 Valid Other IRR onlyRADB 669 99% 67
191.6.252.0/24 Valid Other IRR onlyRADB 669 99% 67
191.6.255.0/24 Valid Other IRR onlyRADB 669 99% 67
191.6.249.0/24 Valid Other IRR onlyRADB 668 99% 66
191.6.251.0/24 Valid Other IRR onlyRADB 667 99% 67
191.6.254.0/24 Valid Other IRR onlyBBOI, RADB 665 99% 67
2804:13ec:8b00::/40 Valid Other IRR onlyRADB 1 0%low visibility 1

AS-SET

AS263302 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 14 are in fix.csv.

  • Route object: RIR9
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
Route object: RIR191.6.248.0/24Route object only in RADB. Add it in the RIR database for the space.672 of 673
Route object: RIR191.6.250.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR191.6.252.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.6.252.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.6.255.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR191.6.249.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR191.6.251.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR191.6.254.0/24Route object only in BBOI, RADB. Add it in the RIR database for the space.665 of 673
Route object: RIR2804:13ec:8b00::/40Route object only in RADB. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

191.6.248.0/21RADB, TCNo ROA
191.6.248.0/22RADBNo ROA
191.6.248.0/23RADBNo ROA
191.6.254.0/23RADBNo ROA
2804:13ec::/32RADB, TCNo 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.