Network · data from 2026-11-12
AS61463 AS61463 - CORPORACION UNIVERSIDAD DE MEDELLIN
Registry name: AS61463 - CORPORACION UNIVERSIDAD DE MEDELLIN, CO · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61463, 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.
| 2800:310:10f::/48 | Invalid: origin | None | 46 7%low visibility |
| 200.34.171.0/24 | Valid | Other IRR onlyRADB | 668 99% |
| 2801:12d::/40 | Valid | Other IRR onlyRADB | 632 99% |
AS-SET
AS61463 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 5 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR2
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2800:310:10f::/48 | ROAs covering it name AS18678, not AS61463. If AS61463 should announce it, add a ROA for AS61463. |
| Route object: none | 2800:310:10f::/48 | No route object for it. Add a route object with origin AS61463 in the RIR database for the space. |
| Route object: RIR | 200.34.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2801:12d::/40 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61463 whose prefix no peer sees AS61463 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2801:0:3c0::/48 | RADB | No 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.