bgpreport

Network · data from 2026-11-12

AS271146 OESTE SERVICOS DE INTERNET

Registry name: AS271146 - OESTE SERVICOS DE INTERNET LTDA., BR · PeeringDB

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

Announced routes

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

179.42.92.0/23 No ROA Other IRR onlyRADB 667 99% 66
2804:76f8::/32 No ROA Other IRR onlyRADB 633 100% 69

AS-SET

AS271146'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: none2
  • Route object: RIR2
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none179.42.92.0/23No ROA covers it. Add a ROA for AS271146, maxLength 23.667 of 673
Route object: RIR179.42.92.0/23Route object only in RADB. Add it in the RIR database for the space.667 of 673
ROA: none2804:76f8::/32No ROA covers it. Add a ROA for AS271146, maxLength 32.633 of 636
Route object: RIR2804:76f8::/32Route object only in RADB. Add it in the RIR database for the space.633 of 636

Route objects not announced

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

179.42.92.0/24RADBNo ROA
179.42.93.0/24RADBNo ROA
2804:76f8::/48RADBNo ROA
2804:76f8:1::/48RADBNo ROA
2804:76f8:ffff::/48RADBNo 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.