Network · data from 2026-11-12
AS204383 SPCom
Registry name: CZ-SPCOM-AS SPCom s.r.o., CZ · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS204383, 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.
| 77.78.78.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.112.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.116.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 81.0.242.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.208.4.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.208.26.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 82.208.32.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 82.208.60.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 85.239.253.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 109.123.206.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 109.123.208.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.232.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.11.246.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 77.78.77.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 77.78.94.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.0.230.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 91.245.8.0/21 | Valid | RIR databaseRIPE | 672 100% |
| 185.250.172.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 2a0c:fc0::/29 | Valid | RIR databaseRIPE | 635 100% |
AS-SET
AS204383's PeeringDB record names no AS-SET.
Fix list
Nothing to change: every route is RPKI valid with a route object in an RIR database, and every route object is announced.
Route objects not announced
Every route object with origin AS204383 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.