Network · data from 2026-11-12
AS218664 prefixlabs-mnt PrefixLabs DOO
Registry name: prefixlabs-mnt PrefixLabs DOO, RS · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS218664, 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.
| 2a0d:d940:3d::/48 | Invalid: origin | None | 112 18% |
| 138.124.98.0/24 | Valid | None | 671 100% |
| 138.124.105.0/24 | Valid | None | 671 100% |
| 138.124.106.0/24 | Valid | None | 671 100% |
| 191.217.248.0/24 | Valid | None | 671 100% |
| 77.239.112.0/24 | Valid | None | 670 100% |
| 81.90.28.0/24 | Valid | None | 670 100% |
| 95.85.254.0/24 | Valid | None | 669 99% |
| 138.124.104.0/24 | Valid | None | 669 99% |
| 138.124.242.0/24 | Valid | None | 669 99% |
| 138.124.243.0/24 | Valid | None | 669 99% |
| 138.124.100.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 187.55.169.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 217.60.66.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 187.55.171.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 31.59.155.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 31.59.165.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 187.55.172.0/24 | Valid | RIR databaseRIPE | 655 97% |
| 187.55.170.0/24 | Valid | RIR databaseRIPE | 17 3%low visibility |
AS-SET
AS218664 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 14 are in fix.csv.
- ROA: origin1
- Route object: none11
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2a0d:d940:3d::/48 | ROAs covering it name AS207567, not AS218664. If AS218664 should announce it, add a ROA for AS218664. |
| Route object: none | 2a0d:d940:3d::/48 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.98.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.105.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.106.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 191.217.248.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 77.239.112.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 81.90.28.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 95.85.254.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.104.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.242.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
| Route object: none | 138.124.243.0/24 | No route object for it. Add a route object with origin AS218664 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS218664 whose prefix no peer sees AS218664 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 187.55.173.0/24 | RIPE | Valid |
| 187.55.174.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.