Network · data from 2026-11-12
AS41368 Spotting Brands Technologies S.L.
Registry name: TVALMANSA-ASN Spotting Brands Technologies S.L., ES · PeeringDB
77IPv4 routes
100.0% RPKI valid · 59.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
31 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
20Route objects not announced
registered with origin AS41368, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS41368, 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.
| 5.183.184.0/23 | Valid | Nonecovered by 5.183.184.0/22 | 673 100% |
| 5.183.186.0/23 | Valid | Nonecovered by 5.183.184.0/22 | 673 100% |
| 89.29.129.0/24 | Valid | Nonecovered by 89.29.128.0/20 | 673 100% |
| 89.29.132.0/24 | Valid | Nonecovered by 89.29.128.0/20 | 673 100% |
| 89.29.133.0/24 | Valid | Nonecovered by 89.29.128.0/20 | 673 100% |
| 89.29.135.0/24 | Valid | Nonecovered by 89.29.128.0/20 | 673 100% |
| 89.29.149.0/24 | Valid | Nonecovered by 89.29.144.0/21 | 673 100% |
| 89.29.150.0/24 | Valid | Nonecovered by 89.29.144.0/21 | 673 100% |
| 89.29.151.0/24 | Valid | Nonecovered by 89.29.144.0/21 | 673 100% |
| 89.29.155.0/24 | Valid | Nonecovered by 89.29.152.0/22 | 673 100% |
| 89.29.233.0/24 | Valid | Nonecovered by 89.29.232.0/22 | 673 100% |
| 89.29.234.0/24 | Valid | Nonecovered by 89.29.232.0/22 | 673 100% |
| 171.22.10.0/24 | Valid | Nonecovered by 171.22.10.0/23 | 673 100% |
| 171.22.11.0/24 | Valid | Nonecovered by 171.22.10.0/23 | 673 100% |
| 176.57.108.0/24 | Valid | Nonecovered by 176.57.108.0/22 | 673 100% |
| 176.57.110.0/23 | Valid | Nonecovered by 176.57.108.0/22 | 673 100% |
| 185.40.39.0/24 | Valid | Nonecovered by 185.40.38.0/23 | 673 100% |
| 185.62.20.0/24 | Valid | Nonecovered by 185.62.20.0/23 | 673 100% |
| 185.62.21.0/24 | Valid | Nonecovered by 185.62.20.0/23 | 673 100% |
| 185.123.56.0/24 | Valid | Nonecovered by 185.123.56.0/22 | 673 100% |
| 185.123.57.0/24 | Valid | Nonecovered by 185.123.56.0/22 | 673 100% |
| 185.123.58.0/24 | Valid | Nonecovered by 185.123.56.0/22 | 673 100% |
| 185.123.59.0/24 | Valid | Other origin onlycovered by 185.123.56.0/22 | 673 100% |
| 193.56.164.0/24 | Valid | Nonecovered by 193.56.164.0/22 | 673 100% |
| 193.56.165.0/24 | Valid | Nonecovered by 193.56.164.0/22 | 673 100% |
| 193.56.166.0/24 | Valid | Nonecovered by 193.56.164.0/22 | 673 100% |
| 193.56.167.0/24 | Valid | Nonecovered by 193.56.164.0/22 | 673 100% |
| 212.119.52.0/24 | Valid | Nonecovered by 212.119.52.0/22 | 673 100% |
| 212.119.53.0/24 | Valid | Nonecovered by 212.119.52.0/22 | 673 100% |
| 212.119.54.0/24 | Valid | Nonecovered by 212.119.52.0/22 | 673 100% |
| 212.119.55.0/24 | Valid | Nonecovered by 212.119.52.0/22 | 673 100% |
| 5.45.169.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.61.200.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.61.203.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.61.206.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 5.61.207.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 81.16.212.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.128.0/20 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.144.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.152.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.156.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.157.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.158.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.159.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.232.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.236.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 89.29.254.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.8.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 171.22.9.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 176.57.104.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 176.57.108.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.40.37.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.62.22.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 185.64.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.240.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.240.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.241.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.242.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.74.243.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.139.176.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.145.40.0/22 | Valid | RIR databaseRIPE | 673 100% |
| 185.214.136.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.214.137.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 185.214.138.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 188.92.124.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 188.92.126.0/23 | Valid | RIR databaseRIPE | 673 100% |
| 5.34.128.0/19 | Valid | RIR databaseRIPE | 672 100% |
| 5.61.204.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 5.61.205.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.16.212.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.16.213.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.16.214.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 81.16.215.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 185.93.80.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 185.214.139.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 212.119.52.0/22 | Valid | RIR databaseRIPE | 672 100% |
| 5.61.202.0/24 | Valid | RIR databaseRIPE | 670 100% |
AS-SET
PeeringDB's irr_as_set for AS41368: AS-TVALMANSA. 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 (AS41368 isn't in the set, or no route object for AS41368 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 | AS41368 in it | Not covered |
|---|---|---|---|---|---|
| AS-TVALMANSA | RIPE | 3 | 1 | 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 51 are in fix.csv.
- Route object: none31
- Route object: not announced20
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.183.184.0/23 | No route object for it. A route object for 5.183.184.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 5.183.186.0/23 | No route object for it. A route object for 5.183.184.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.129.0/24 | No route object for it. A route object for 89.29.128.0/20 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.132.0/24 | No route object for it. A route object for 89.29.128.0/20 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.133.0/24 | No route object for it. A route object for 89.29.128.0/20 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.135.0/24 | No route object for it. A route object for 89.29.128.0/20 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.149.0/24 | No route object for it. A route object for 89.29.144.0/21 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.150.0/24 | No route object for it. A route object for 89.29.144.0/21 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.151.0/24 | No route object for it. A route object for 89.29.144.0/21 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.155.0/24 | No route object for it. A route object for 89.29.152.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.233.0/24 | No route object for it. A route object for 89.29.232.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 89.29.234.0/24 | No route object for it. A route object for 89.29.232.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 171.22.10.0/24 | No route object for it. A route object for 171.22.10.0/23 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 171.22.11.0/24 | No route object for it. A route object for 171.22.10.0/23 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 176.57.108.0/24 | No route object for it. A route object for 176.57.108.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 176.57.110.0/23 | No route object for it. A route object for 176.57.108.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.40.39.0/24 | No route object for it. A route object for 185.40.38.0/23 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.62.20.0/24 | No route object for it. A route object for 185.62.20.0/23 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.62.21.0/24 | No route object for it. A route object for 185.62.20.0/23 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.123.56.0/24 | No route object for it. A route object for 185.123.56.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.123.57.0/24 | No route object for it. A route object for 185.123.56.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.123.58.0/24 | No route object for it. A route object for 185.123.56.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 185.123.59.0/24 | Route objects for it name AS203709. A route object for 185.123.56.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 193.56.164.0/24 | No route object for it. A route object for 193.56.164.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 193.56.165.0/24 | No route object for it. A route object for 193.56.164.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 193.56.166.0/24 | No route object for it. A route object for 193.56.164.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 193.56.167.0/24 | No route object for it. A route object for 193.56.164.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 212.119.52.0/24 | No route object for it. A route object for 212.119.52.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 212.119.53.0/24 | No route object for it. A route object for 212.119.52.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 212.119.54.0/24 | No route object for it. A route object for 212.119.52.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
| Route object: none | 212.119.55.0/24 | No route object for it. A route object for 212.119.52.0/22 with origin AS41368 covers it (filters allowing more-specifics accept it). Add a route object with origin AS41368 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS41368 whose prefix no peer sees AS41368 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.183.184.0/22 | RIPE | Valid |
| 5.183.184.0/24 | RIPE | Valid |
| 5.183.185.0/24 | RIPE | Valid |
| 5.183.186.0/24 | RIPE | Valid |
| 5.183.187.0/24 | RIPE | Valid |
| 89.29.128.0/19 | RIPE | No ROA |
| 89.29.156.0/22 | RIPE | No ROA |
| 171.22.8.0/22 | RIPE | Valid |
| 171.22.10.0/23 | RIPE | Valid |
| 176.57.104.0/21 | RIPE | No ROA |
| 185.40.38.0/23 | RIPE | Valid |
| 185.62.20.0/23 | RIPE | Valid |
| 185.123.56.0/22 | RIPE | Valid |
| 185.139.176.0/24 | RIPE | Invalid: maxLength |
| 185.139.177.0/24 | RIPE | Invalid: maxLength |
| 185.139.178.0/24 | RIPE | Invalid: maxLength |
| 185.139.179.0/24 | RIPE | Invalid: maxLength |
| 188.92.124.0/22 | RIPE | Valid |
| 193.56.164.0/22 | RIPE | Valid |
| 2a00:4b80:3::/48 | 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.