bgpreport

Network · data from 2026-11-12

AS272606 AS272606 - DNS FIBRA LTDA

Registry name: AS272606 - DNS FIBRA LTDA, 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
0Route objects not announced registered with origin AS272606, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS272606, 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.185.104.0/23 No ROA Other IRR onlyTC 670 100% 67
177.185.104.0/24 No ROA Other IRR onlyTC 669 99% 67
177.185.105.0/24 No ROA Other IRR onlyTC 669 99% 67
2804:85e0::/32 No ROA Other IRR onlyRADB, TC 635 100% 67
2804:85e0:400::/38 No ROA Other IRR onlyTC 2 0%low visibility 2
2804:85e0:400::/39 No ROA Other IRR onlyTC 2 0%low visibility 2

AS-SET

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

  • ROA: none6
  • Route object: RIR6
ChangePrefix or setDetailFull-table peers
ROA: none177.185.104.0/23No ROA covers it. Add a ROA for AS272606, maxLength 23.670 of 673
Route object: RIR177.185.104.0/23Route object only in TC. Add it in the RIR database for the space.670 of 673
ROA: none177.185.104.0/24No ROA covers it. Add a ROA for AS272606, maxLength 24.669 of 673
Route object: RIR177.185.104.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none177.185.105.0/24No ROA covers it. Add a ROA for AS272606, maxLength 24.669 of 673
Route object: RIR177.185.105.0/24Route object only in TC. Add it in the RIR database for the space.669 of 673
ROA: none2804:85e0::/32No ROA covers it. Add a ROA for AS272606, maxLength 32.635 of 636
Route object: RIR2804:85e0::/32Route object only in RADB, TC. Add it in the RIR database for the space.635 of 636
ROA: none2804:85e0:400::/38No ROA covers it. Add a ROA for AS272606, maxLength 38.2 of 636
Route object: RIR2804:85e0:400::/38Route object only in TC. Add it in the RIR database for the space.2 of 636
ROA: none2804:85e0:400::/39No ROA covers it. Add a ROA for AS272606, maxLength 39.2 of 636
Route object: RIR2804:85e0:400::/39Route object only in TC. Add it in the RIR database for the space.2 of 636

Route objects not announced

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