bgpreport

Network · data from 2026-11-12

AS270588 AS270588 - LITORAL CONECT - SAO SEBASTIAO - SP

Registry name: AS270588 - LITORAL CONECT - SAO SEBASTIAO - SP, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS270588, 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.129.36.0/22 No ROA Other IRR onlyRADB, TC 671 100% 67
177.129.36.0/23 No ROA Other IRR onlyRADB, TC 669 99% 67
177.129.38.0/23 No ROA Other IRR onlyRADB, TC 669 99% 67
2804:6e50::/32 No ROA Other IRR onlyRADB, TC 631 99% 67
2804:6e50::/33 No ROA Other IRR onlyTC 1 0%low visibility 1
2804:6e50:8000::/33 No ROA Other IRR onlyTC 1 0%low visibility 1

AS-SET

AS270588 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 13 are in fix.csv.

  • ROA: none6
  • Route object: RIR6
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none177.129.36.0/22No ROA covers it. Add a ROA for AS270588, maxLength 22.671 of 673
Route object: RIR177.129.36.0/22Route object only in RADB, TC. Add it in the RIR database for the space.671 of 673
ROA: none177.129.36.0/23No ROA covers it. Add a ROA for AS270588, maxLength 23.669 of 673
Route object: RIR177.129.36.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none177.129.38.0/23No ROA covers it. Add a ROA for AS270588, maxLength 23.669 of 673
Route object: RIR177.129.38.0/23Route object only in RADB, TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:6e50::/32No ROA covers it. Add a ROA for AS270588, maxLength 32.631 of 636
Route object: RIR2804:6e50::/32Route object only in RADB, TC. Add it in the RIR database for the space.631 of 636
ROA: none2804:6e50::/33No ROA covers it. Add a ROA for AS270588, maxLength 33.1 of 636
Route object: RIR2804:6e50::/33Route object only in TC. Add it in the RIR database for the space.1 of 636
ROA: none2804:6e50:8000::/33No ROA covers it. Add a ROA for AS270588, maxLength 33.1 of 636
Route object: RIR2804:6e50:8000::/33Route object only in TC. Add it in the RIR database for the space.1 of 636

Route objects not announced

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

177.129.37.0/24RADBNo 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.