Network · data from 2026-11-12
AS209100 tpnet TP NET Plus s.r.o
Registry name: tpnet TP NET Plus s.r.o, SK · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS209100, 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.
| 188.190.100.0/22 | No ROA | RIR databaseRIPE | 671 100% |
AS-SET
AS209100 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 18 are in fix.csv.
- ROA: none1
- Route object: not announced17
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 188.190.100.0/22 | No ROA covers it. Add a ROA for AS209100, maxLength 22. |
Route objects not announced
Route objects with origin AS209100 whose prefix no peer sees AS209100 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2404:f4c0:fc00::/44 | ALTDB | Invalid: origin |
| 2404:f4c0:fc00::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc01::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc02::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc03::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc04::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc05::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc06::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc07::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc08::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc09::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0a::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0b::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0c::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0d::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0e::/48 | ALTDB | Invalid: origin |
| 2404:f4c0:fc0f::/48 | ALTDB | 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.