bgpreport

Network · data from 2026-11-12

AS262866 TURBO 10 Telecomunicações

Registry name: AS262866 - TURBO 10 Telecomunicacoes Ltda., BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 50.0% with a route object
3IPv6 routes 100.0% RPKI valid · 100.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No 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 AS262866, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS262866, 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.
177.12.245.0/24 Valid Nonecovered by 177.12.240.0/21 669 99% 66
177.12.248.0/21 Valid Nonecovered by 177.12.240.0/20 669 99% 66
177.12.240.0/20 Valid Other IRR onlyRADB, TC 670 100% 66
177.12.240.0/21 Valid Other IRR onlyRADB 669 99% 67
2804:5eb8:8000::/33 Valid Other IRR onlyRADB 634 100% 69
2804:5eb8::/32 Valid Other IRR onlyRADB, TC 632 99% 69
2804:5eb8::/33 Valid Other IRR onlyRADB 632 99% 67

AS-SET

AS262866'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 10 are in fix.csv.

  • Route object: none2
  • Route object: RIR5
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
Route object: none177.12.245.0/24No route object for it. A route object for 177.12.240.0/21 with origin AS262866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262866 in the RIR database for the space.669 of 673
Route object: none177.12.248.0/21No route object for it. A route object for 177.12.240.0/20 with origin AS262866 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262866 in the RIR database for the space.669 of 673
Route object: RIR177.12.240.0/20Route object only in RADB, TC. Add it in the RIR database for the space.670 of 673
Route object: RIR177.12.240.0/21Route object only in RADB. Add it in the RIR database for the space.669 of 673
Route object: RIR2804:5eb8:8000::/33Route object only in RADB. Add it in the RIR database for the space.634 of 636
Route object: RIR2804:5eb8::/32Route object only in RADB, TC. Add it in the RIR database for the space.632 of 636
Route object: RIR2804:5eb8::/33Route object only in RADB. Add it in the RIR database for the space.632 of 636

Route objects not announced

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

177.12.240.0/24RADBValid
177.12.242.0/23RADBValid
2804:5eb8:a000::/44RADBValid

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.