Network · data from 2026-11-12
AS219122 EXPONET
Registry name: EXPONET EXPONET VERI MERKEZI HIZMETLERI SAN. VE TIC. LTD. STI., TR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS219122, 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.56.29.0/24 | Invalid: origin | Other origin only | 131 19% |
| 130.78.8.0/24 | Invalid: origin | Other origin only | 1 0%low visibility |
| 9.247.144.0/24 | Valid | RIR databaseRIPE | 672 100% |
AS-SET
AS219122'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 4 are in fix.csv.
- ROA: origin2
- Route object: none2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 5.56.29.0/24 | ROAs covering it name AS219048, not AS219122. If AS219122 should announce it, add a ROA for AS219122. |
| Route object: none | 5.56.29.0/24 | Route objects for it name AS219048. Add a route object with origin AS219122 in the RIR database for the space. |
| ROA: origin | 130.78.8.0/24 | ROAs covering it name AS203114, not AS219122. If AS219122 should announce it, add a ROA for AS219122. |
| Route object: none | 130.78.8.0/24 | Route objects for it name AS203114. Add a route object with origin AS219122 in the RIR database for the space. |
Route objects not announced
Every route object with origin AS219122 is announced.
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.