Network · data from 2026-11-12
AS31435 MEDICOM-BG Medicom Bulgaria Ltd.
Registry name: MEDICOM-BG Medicom Bulgaria Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS31435, 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.
| 84.238.226.54/32 | Invalid: maxLength | Nonecovered by 84.238.224.0/22 | 3 0%low visibility |
| 84.238.226.207/32 | Invalid: maxLength | Nonecovered by 84.238.224.0/22 | 3 0%low visibility |
| 82.146.20.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.146.22.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.146.26.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 84.238.208.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 84.238.220.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 84.238.222.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 84.238.224.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 84.238.220.0/23 | Valid | RIR databaseRIPE | 316 47% |
AS-SET
AS31435 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 7 are in fix.csv.
- ROA: maxLength2
- Route object: none2
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 84.238.226.54/32 | ROA 84.238.224.0/22 AS31435 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 84.238.226.54/32. |
| Route object: none | 84.238.226.54/32 | No route object for it. A route object for 84.238.224.0/22 with origin AS31435 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS31435 in the RIR database for the space. |
| ROA: maxLength | 84.238.226.207/32 | ROA 84.238.224.0/22 AS31435 has maxLength 22; the route is a /32. Raise the maxLength, or add a ROA for 84.238.226.207/32. |
| Route object: none | 84.238.226.207/32 | No route object for it. A route object for 84.238.224.0/22 with origin AS31435 covers it (too long for filters allowing more-specifics up to /24). Add a route object with origin AS31435 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS31435 whose prefix no peer sees AS31435 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 82.146.22.0/23 | RIPE | No ROA |
| 84.238.248.0/23 | RIPE | Invalid: origin |
| 185.240.152.0/22 | RIPE | 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.