Network · data from 2026-11-12
AS215367 LIXER
Registry name: LIXER LENIN JABIB RAMIREZ, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS215367, 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.
| 2a0f:85c1:8cd::/48 | No ROA | None | 633 100% |
| 128.254.204.0/24 | Valid | RIR databaseARIN | 671 100% |
| 160.202.135.0/24 | Valid | RIR databaseRIPE | 667 99% |
AS-SET
AS215367's PeeringDB record names no 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 7 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 2a0f:85c1:8cd::/48 | No ROA covers it. Add a ROA for AS215367, maxLength 48. |
| Route object: none | 2a0f:85c1:8cd::/48 | No route object for it. Add a route object with origin AS215367 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS215367 whose prefix no peer sees AS215367 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a14:7c0:b002::/48 | RIPE | Invalid: origin |
| 2a14:7c4:b00b::/48 | RIPE | Invalid: origin |
| 2a14:7c5:b00b::/48 | RIPE | Invalid: origin |
| 2a14:7c6:b00b::/48 | RIPE | Invalid: origin |
| 2a14:7c7:b00b::/48 | RIPE | Invalid: origin |
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.