bgpreport

Network · data from 2026-11-12

AS271532 TURBONET SERVIÇOS DE COMUNICAÇAO EIRELI

Registry name: AS271532 - TURBONET SERVICOS DE COMUNICACAO EIRELI, BR · PeeringDB

4IPv4 routes 100.0% RPKI valid · 75.0% with a route object
3IPv6 routes 66.7% RPKI valid · 66.7% with a route object
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
1Route objects not announced registered with origin AS271532, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS271532, 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.
2804:2884:8034::/47 No ROA None 636 100% 67
181.224.56.0/24 Valid Nonecovered by 181.224.56.0/22 669 99% 67
181.224.59.0/24 Valid Other IRR onlyRADB 671 100% 67
181.224.58.0/24 Valid Other IRR onlyRADB 670 100% 66
181.224.57.0/24 Valid Other IRR onlyRADB 668 99% 66
2804:7d00::/32 Valid Other IRR onlyALTDB, RADB, TC 635 100% 67
2804:7d00:e000::/40 Valid Other IRR onlyRADB 633 100% 67

AS-SET

AS271532'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 9 are in fix.csv.

  • ROA: none1
  • Route object: none2
  • Route object: RIR5
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:2884:8034::/47No ROA covers it. Add a ROA for AS271532, maxLength 47.636 of 636
Route object: none2804:2884:8034::/47No route object for it. Add a route object with origin AS271532 in the RIR database for the space.636 of 636
Route object: none181.224.56.0/24No route object for it. A route object for 181.224.56.0/22 with origin AS271532 covers it (filters allowing more-specifics accept it). Add a route object with origin AS271532 in the RIR database for the space.669 of 673
Route object: RIR181.224.59.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR181.224.58.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR181.224.57.0/24Route object only in RADB. Add it in the RIR database for the space.668 of 673
Route object: RIR2804:7d00::/32Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:7d00:e000::/40Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

181.224.56.0/22RADB, 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.