Network · data from 2026-11-12
AS47849 NETCOMLAN-AS Global Communication Net Plc
Registry name: NETCOMLAN-AS Global Communication Net Plc, BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS47849, 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.
| 109.160.76.0/23 | No ROA | RIR databaseRIPE | 1 0%low visibility |
| 83.222.162.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.165.223.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.5.32.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 212.5.55.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.70.134.0/23 | Valid | RIR databaseRIPE | 672 100% |
| 212.70.138.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS47849 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 4 are in fix.csv.
- ROA: none1
- Route object: not announced3
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 109.160.76.0/23 | No ROA covers it. Add a ROA for AS47849, maxLength 23. |
Route objects not announced
Route objects with origin AS47849 whose prefix no peer sees AS47849 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 212.70.134.0/24 | RIPE | Valid |
| 212.70.135.0/24 | RIPE | Valid |
| 212.70.136.0/23 | 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.