bgpreport

Network · data from 2026-11-12

AS270902 AS270902 - R H DE PAULA - EPP

Registry name: AS270902 - R H DE PAULA - EPP, BR · not in PeeringDB

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

Announced routes

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

189.50.36.0/22 No ROA Other IRR onlyALTDB, RADB, TC 667 99% 67

AS-SET

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

  • ROA: none1
  • Route object: RIR1
  • Route object: not announced5
ChangePrefix or setDetailFull-table peers
ROA: none189.50.36.0/22No ROA covers it. Add a ROA for AS270902, maxLength 22.667 of 673
Route object: RIR189.50.36.0/22Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space.667 of 673

Route objects not announced

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

189.50.36.0/24RADB, TCNo ROA
189.50.37.0/24RADBNo ROA
189.50.38.0/24RADB, TCNo ROA
189.50.39.0/24RADB, TCNo ROA
2804:7334::/32ALTDB, RADB, 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.