bgpreport

Network · data from 2026-11-12

AS268796 AS268796 - D.A.S PROVEDOR DE INTERNET FIBRA OTICA E BANDA

Registry name: AS268796 - D.A.S PROVEDOR DE INTERNET FIBRA OTICA E BANDA, BR · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS268796, 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:5ac8::/34 No ROA Nonecovered by 2804:5ac8::/33 630 99% 67
2804:5ac8:8000::/34 No ROA Nonecovered by 2804:5ac8:8000::/33 630 99% 67
2804:5ac8:c000::/35 No ROA Nonecovered by 2804:5ac8:8000::/33 630 99% 67
2804:5ac8:e000::/35 No ROA Nonecovered by 2804:5ac8:8000::/33 630 99% 67
45.172.212.0/23 No ROA Other IRR onlyRADB 668 99% 67
45.172.214.0/23 No ROA Other IRR onlyRADB 668 99% 66

AS-SET

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

  • ROA: none6
  • Route object: none4
  • Route object: RIR2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2804:5ac8::/34No ROA covers it. Add a ROA for AS268796, maxLength 34.630 of 636
Route object: none2804:5ac8::/34No route object for it. A route object for 2804:5ac8::/33 with origin AS268796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268796 in the RIR database for the space.630 of 636
ROA: none2804:5ac8:8000::/34No ROA covers it. Add a ROA for AS268796, maxLength 34.630 of 636
Route object: none2804:5ac8:8000::/34No route object for it. A route object for 2804:5ac8:8000::/33 with origin AS268796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268796 in the RIR database for the space.630 of 636
ROA: none2804:5ac8:c000::/35No ROA covers it. Add a ROA for AS268796, maxLength 35.630 of 636
Route object: none2804:5ac8:c000::/35No route object for it. A route object for 2804:5ac8:8000::/33 with origin AS268796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268796 in the RIR database for the space.630 of 636
ROA: none2804:5ac8:e000::/35No ROA covers it. Add a ROA for AS268796, maxLength 35.630 of 636
Route object: none2804:5ac8:e000::/35No route object for it. A route object for 2804:5ac8:8000::/33 with origin AS268796 covers it (filters allowing more-specifics accept it). Add a route object with origin AS268796 in the RIR database for the space.630 of 636
ROA: none45.172.212.0/23No ROA covers it. Add a ROA for AS268796, maxLength 23.668 of 673
Route object: RIR45.172.212.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673
ROA: none45.172.214.0/23No ROA covers it. Add a ROA for AS268796, maxLength 23.668 of 673
Route object: RIR45.172.214.0/23Route object only in RADB. Add it in the RIR database for the space.668 of 673

Route objects not announced

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

2804:5ac8::/33RADBNo ROA
2804:5ac8:8000::/33RADBNo 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.