Network · data from 2026-11-12
AS61304 CONNECTAZ-AS Connect CJSC
Registry name: CONNECTAZ-AS Connect CJSC, AZ · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS61304, 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.
| 185.12.16.0/24 | Invalid: origin | Other origin only | 2 0%low visibility |
AS-SET
AS61304 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 7 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 185.12.16.0/24 | ROAs covering it name AS39232, not AS61304. If AS61304 should announce it, add a ROA for AS61304. |
| Route object: none | 185.12.16.0/24 | Route objects for it name AS39232. Add a route object with origin AS61304 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS61304 whose prefix no peer sees AS61304 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 94.20.164.0/24 | RIPE | Invalid: maxLength |
| 94.20.165.0/24 | RIPE | Invalid: maxLength |
| 94.20.166.0/24 | RIPE | Invalid: maxLength |
| 94.20.167.0/24 | RIPE | Invalid: maxLength |
| 2a02:ecc0::/29 | 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.