bgpreport

Network · data from 2026-11-12

AS274705 AS274705 - PUMANET TELECOM LTDA

Registry name: AS274705 - PUMANET TELECOM LTDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS274705, 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:9254::/32 No ROA Other IRR onlyBBOI, NTTCOM, RADB, TC 636 100% 67

AS-SET

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

  • ROA: none1
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: none2804:9254::/32No ROA covers it. Add a ROA for AS274705, maxLength 32.636 of 636
Route object: RIR2804:9254::/32Route object only in BBOI, NTTCOM, RADB, TC. Add it in the RIR database for the space.636 of 636

Route objects not announced

Every route object with origin AS274705 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.