bgpreport

Network · data from 2026-11-12

AS271833 AS271833 - MUNICIPIO DE MEDELLIN

Registry name: AS271833 - MUNICIPIO DE MEDELLIN, CO · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS271833, 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.
2801:1d6:0:1::/64 Invalid: maxLength Nonecovered by 2801:1d6::/40 6 1%low visibility 6
2801:1d6:0:20::/64 Invalid: maxLength Nonecovered by 2801:1d6::/40 6 1%low visibility 6
2801:1d6:0:151::/64 Invalid: maxLength Nonecovered by 2801:1d6::/40 6 1%low visibility 6
2801:1d6:0:c13::/64 Invalid: maxLength Nonecovered by 2801:1d6::/40 6 1%low visibility 6
2801:1d6::/40 Valid Other IRR onlyRADB 635 100% 67

AS-SET

AS271833 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 9 are in fix.csv.

  • ROA: maxLength4
  • Route object: none4
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
ROA: maxLength2801:1d6:0:1::/64ROA 2801:1d6::/40 AS271833 has maxLength 40; the route is a /64. Raise the maxLength, or add a ROA for 2801:1d6:0:1::/64.6 of 636
Route object: none2801:1d6:0:1::/64No route object for it. A route object for 2801:1d6::/40 with origin AS271833 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS271833 in the RIR database for the space.6 of 636
ROA: maxLength2801:1d6:0:20::/64ROA 2801:1d6::/40 AS271833 has maxLength 40; the route is a /64. Raise the maxLength, or add a ROA for 2801:1d6:0:20::/64.6 of 636
Route object: none2801:1d6:0:20::/64No route object for it. A route object for 2801:1d6::/40 with origin AS271833 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS271833 in the RIR database for the space.6 of 636
ROA: maxLength2801:1d6:0:151::/64ROA 2801:1d6::/40 AS271833 has maxLength 40; the route is a /64. Raise the maxLength, or add a ROA for 2801:1d6:0:151::/64.6 of 636
Route object: none2801:1d6:0:151::/64No route object for it. A route object for 2801:1d6::/40 with origin AS271833 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS271833 in the RIR database for the space.6 of 636
ROA: maxLength2801:1d6:0:c13::/64ROA 2801:1d6::/40 AS271833 has maxLength 40; the route is a /64. Raise the maxLength, or add a ROA for 2801:1d6:0:c13::/64.6 of 636
Route object: none2801:1d6:0:c13::/64No route object for it. A route object for 2801:1d6::/40 with origin AS271833 covers it (too long for filters allowing more-specifics up to /48). Add a route object with origin AS271833 in the RIR database for the space.6 of 636
Route object: RIR2801:1d6::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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