Network · data from 2026-11-12
AS210064 Dimit-Network-Technology Dimit Network Technology Company LLC
Registry name: Dimit-Network-Technology Dimit Network Technology Company LLC, IR · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS210064, 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.
| 91.192.160.0/24 | Invalid: origin | None | 2 0%low visibility |
| 91.198.110.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
AS210064 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 | 91.192.160.0/24 | ROAs covering it name AS16628, not AS210064. If AS210064 should announce it, add a ROA for AS210064. |
| Route object: none | 91.192.160.0/24 | No route object for it. Add a route object with origin AS210064 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS210064 whose prefix no peer sees AS210064 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 185.187.51.0/24 | RIPE | Valid |
| 185.221.239.0/24 | 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.