Network · data from 2026-11-12
AS213570 Hostluyoruz
Registry name: Rowenix ROWENIX DIGITAL SOLUTIONS LLC, US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS213570, 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.
| 87.76.136.0/24 | Invalid: origin | Other origin only | 10 1%low visibility |
| 31.58.236.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 187.54.8.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 77.67.29.0/24 | Valid | RIR databaseRADB, RIPE | 664 99% |
AS-SET
AS213570'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 3 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 87.76.136.0/24 | ROAs covering it name AS218231, not AS213570. If AS213570 should announce it, add a ROA for AS213570. |
| Route object: none | 87.76.136.0/24 | Route objects for it name AS218231. Add a route object with origin AS213570 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS213570 whose prefix no peer sees AS213570 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a0f:85c1:b42::/48 | 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.