Network · data from 2026-11-12
AS44828 Neterra_Enterprise_Internet_Access Neterra Ltd.
Registry name: Neterra_Enterprise_Internet_Access Neterra Ltd., BG · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS44828, 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.
| 87.120.191.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
| 31.13.224.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.121.133.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 87.121.220.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 94.154.161.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 87.120.33.0/24 | Valid | RIR databaseRIPE | 669 99% |
AS-SET
AS44828 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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 87.120.191.0/24 | ROAs covering it name AS133495, not AS44828. If AS44828 should announce it, add a ROA for AS44828. |
| Route object: none | 87.120.191.0/24 | Route objects for it name AS212827. Add a route object with origin AS44828 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS44828 whose prefix no peer sees AS44828 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.139.123.0/24 | RIPE | Valid |
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.