bgpreport

Network · data from 2026-11-12

AS274370 AS274370 - IPB NET LTDA

Registry name: AS274370 - IPB NET LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274370, 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:96f0::/32 No ROA Other IRR onlyRADB, TC 634 100% 67
189.28.56.0/24 Valid None 526 78% 67

AS-SET

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

  • ROA: none1
  • Route object: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2804:96f0::/32No ROA covers it. Add a ROA for AS274370, maxLength 32.634 of 636
Route object: RIR2804:96f0::/32Route object only in RADB, TC. Add it in the RIR database for the space.634 of 636
Route object: none189.28.56.0/24No route object for it. Add a route object with origin AS274370 in the RIR database for the space.526 of 673

Route objects not announced

Every route object with origin AS274370 is announced.

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.