Network · data from 2026-11-12
AS43043 AUROLOGIC-BYOIP aurologic GmbH
Registry name: AUROLOGIC-BYOIP aurologic GmbH, DE · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS43043, 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.
| 45.66.151.0/24 | Invalid: origin | Other origin only | 8 1%low visibility |
| 2a0e:b540:acac::/48 | Valid | RIR databaseRIPE | 634 100% |
AS-SET
AS43043 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: origin1
- Route object: none1
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 45.66.151.0/24 | ROAs covering it name AS393942, not AS43043. If AS43043 should announce it, add a ROA for AS43043. |
| Route object: none | 45.66.151.0/24 | Route objects for it name AS393942. Add a route object with origin AS43043 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS43043 whose prefix no peer sees AS43043 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 83.137.154.0/23 | RIPE | Valid |
| 191.96.248.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.