Network · data from 2026-11-12
AS199490 INTERCONNECT s.r.o.
Registry name: INTERCONNECT INTERCONNECT s.r.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS199490, 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.
| 45.84.164.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.14.232.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a02:f000::/32 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS199490: AS199490:AS-ALL. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS199490 isn't in the set, or no route object for AS199490 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.
| Name | Database | ASNs | Sets | AS199490 in it | Not covered |
|---|---|---|---|---|---|
| AS199490:AS-ALL | RIPE1 member set in no database: AS200635:AS-CUSTOMERS | 3 | 5 | Yes | 0 |
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 1 are in fix.csv.
- AS-SET: missing member1
| Change | Prefix or set | Detail |
|---|---|---|
| AS-SET: missing member | AS199490:AS-ALL | AS199490:AS-ALL (RIPE) lists AS200635:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS199490 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.