Network · data from 2026-11-12
AS30938 abstation ahbr company limited
Registry name: abstation ahbr company limited, GB · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS30938, 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.
| 5.39.250.0/24 | Invalid: origin | Other origin only | 19 3%low visibility |
| 31.192.240.0/21 | Valid | None | 673 100% |
| 5.39.248.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.178.97.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.5.36.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 45.12.216.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS30938 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 8 are in fix.csv.
- ROA: origin1
- Route object: none2
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.39.250.0/24 | ROAs covering it name AS41745, not AS30938. If AS30938 should announce it, add a ROA for AS30938. |
| Route object: none | 5.39.250.0/24 | Route objects for it name AS41745. Add a route object with origin AS30938 in the RIR database for the space. |
| Route object: none | 31.192.240.0/21 | No route object for it. Add a route object with origin AS30938 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS30938 whose prefix no peer sees AS30938 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 31.192.240.0/24 | RIPE | Valid |
| 31.192.241.0/24 | RIPE | Valid |
| 31.192.242.0/24 | RIPE | Valid |
| 31.192.243.0/24 | RIPE | Valid |
| 31.192.245.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.