bgpreport

Network · data from 2026-11-12

AS272676 AS272676 - Brasil Provedor de Internet

Registry name: AS272676 - Brasil Provedor de Internet, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS272676, 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:86f0::/32 No ROA Other IRR onlyRADB 631 99% 67
2804:86f0::/33 No ROA Other IRR onlyRADB 631 99% 67
2804:86f0:8000::/33 No ROA Other IRR onlyRADB 631 99% 67
209.61.50.0/24 Valid Nonecovered by 209.61.50.0/23 670 100% 67
209.61.51.0/24 Valid Nonecovered by 209.61.50.0/23 670 100% 67
209.61.50.0/23 Valid Other IRR onlyRADB 672 100% 67

AS-SET

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

  • ROA: none3
  • Route object: none2
  • Route object: RIR4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: none2804:86f0::/32No ROA covers it. Add a ROA for AS272676, maxLength 32.631 of 636
Route object: RIR2804:86f0::/32Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:86f0::/33No ROA covers it. Add a ROA for AS272676, maxLength 33.631 of 636
Route object: RIR2804:86f0::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
ROA: none2804:86f0:8000::/33No ROA covers it. Add a ROA for AS272676, maxLength 33.631 of 636
Route object: RIR2804:86f0:8000::/33Route object only in RADB. Add it in the RIR database for the space.631 of 636
Route object: none209.61.50.0/24No route object for it. A route object for 209.61.50.0/23 with origin AS272676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272676 in the RIR database for the space.670 of 673
Route object: none209.61.51.0/24No route object for it. A route object for 209.61.50.0/23 with origin AS272676 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272676 in the RIR database for the space.670 of 673
Route object: RIR209.61.50.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

38.226.53.0/24ARINValid

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.