bgpreport

Network · data from 2026-11-12

AS262856 Mil Negocios LTDA.

Registry name: AS262856 - Mil Negocios LTDA., BR · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS262856, 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.10.208.0/22 Valid Nonecovered by 177.10.208.0/21 672 100% 66
177.10.212.0/22 Valid Nonecovered by 177.10.208.0/21 672 100% 66
177.10.215.0/24 Valid Nonecovered by 177.10.208.0/21 672 100% 66
2804:4050::/34 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050:aa7::/48 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050:bb7::/48 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050:4000::/34 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050:8000::/34 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050:c000::/34 Valid Nonecovered by 2804:4050::/32 634 100% 67
2804:4050::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
2804:4050:2000::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
2804:4050:4000::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
2804:4050:6000::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
2804:4050:8000::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
2804:4050:a000::/35 Valid Nonecovered by 2804:4050::/32 362 57% 65
177.10.208.0/23 Valid Nonecovered by 177.10.208.0/21 214 32% 57
177.10.210.0/23 Valid Nonecovered by 177.10.208.0/21 214 32% 57
177.10.214.0/23 Valid Nonecovered by 177.10.208.0/21 214 32% 57
177.10.212.0/23 Valid Nonecovered by 177.10.208.0/21 213 32% 57
177.10.213.0/24 Valid Nonecovered by 177.10.208.0/21 3 0%low visibility 4
177.10.214.0/24 Valid Nonecovered by 177.10.208.0/21 2 0%low visibility 3
177.10.208.0/21 Valid Other IRR onlyRADB, TC 672 100% 66

AS-SET

AS262856's PeeringDB record names no 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 23 are in fix.csv.

  • Route object: none21
  • Route object: RIR1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
Route object: none177.10.208.0/22No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.672 of 673
Route object: none177.10.212.0/22No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.672 of 673
Route object: none177.10.215.0/24No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.672 of 673
Route object: none2804:4050::/34No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050:aa7::/48No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050:bb7::/48No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050:4000::/34No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050:8000::/34No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050:c000::/34No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.634 of 636
Route object: none2804:4050::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none2804:4050:2000::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none2804:4050:4000::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none2804:4050:6000::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none2804:4050:8000::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none2804:4050:a000::/35No route object for it. A route object for 2804:4050::/32 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.362 of 636
Route object: none177.10.208.0/23No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.214 of 673
Route object: none177.10.210.0/23No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.214 of 673
Route object: none177.10.214.0/23No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.214 of 673
Route object: none177.10.212.0/23No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.213 of 673
Route object: none177.10.213.0/24No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.3 of 673
Route object: none177.10.214.0/24No route object for it. A route object for 177.10.208.0/21 with origin AS262856 covers it (filters allowing more-specifics accept it). Add a route object with origin AS262856 in the RIR database for the space.2 of 673
Route object: RIR177.10.208.0/21Route object only in RADB, TC. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

2804:4050::/32RADB, TCValid

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.