Network · data from 2026-11-12
AS202632 TXtv TXTV d.o.o. Tuzla
Registry name: TXtv TXTV d.o.o. Tuzla, BA · not in PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS202632, 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.
| 31.47.0.0/24 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 31.47.4.0/23 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 31.47.8.0/24 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 31.47.9.0/24 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 31.47.10.0/24 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 31.47.14.0/23 | Valid | Nonecovered by 31.47.0.0/19 | 673 100% |
| 185.210.181.0/24 | Valid | Nonecovered by 185.210.180.0/22 | 673 100% |
| 185.210.182.0/24 | Valid | Nonecovered by 185.210.180.0/22 | 673 100% |
| 31.47.0.0/19 | Valid | RIR databaseRIPE | 673 100% |
| 31.47.16.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 185.12.168.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.173.28.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.210.180.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.64.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.64.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.68.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.112.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.124.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.125.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.126.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 213.91.127.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.71.48.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 217.71.56.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 2a03:9240::/32 | Valid | RIR databaseRIPE | 636 100% |
AS-SET
AS202632 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 19 are in fix.csv.
- Route object: none8
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 31.47.0.0/24 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 31.47.4.0/23 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 31.47.8.0/24 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 31.47.9.0/24 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 31.47.10.0/24 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 31.47.14.0/23 | No route object for it. A route object for 31.47.0.0/19 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 185.210.181.0/24 | No route object for it. A route object for 185.210.180.0/22 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
| Route object: none | 185.210.182.0/24 | No route object for it. A route object for 185.210.180.0/22 with origin AS202632 covers it (filters allowing more-specifics accept it). Add a route object with origin AS202632 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS202632 whose prefix no peer sees AS202632 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 209.162.200.0/24 | RIPE | Invalid: origin |
| 213.91.112.0/21 | RIPE | Valid |
| 213.91.120.0/22 | RIPE | Invalid: maxLength |
| 213.91.120.0/24 | RIPE | Invalid: maxLength |
| 213.91.121.0/24 | RIPE | Invalid: maxLength |
| 213.91.122.0/24 | RIPE | Invalid: maxLength |
| 213.91.123.0/24 | RIPE | Invalid: maxLength |
| 2a03:9240::/48 | RIPE | Invalid: maxLength |
| 2a03:9240:1::/48 | RIPE | Invalid: maxLength |
| 2a03:9240:2::/48 | RIPE | Invalid: maxLength |
| 2a03:9240:3::/48 | RIPE | Invalid: maxLength |
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.