Network · data from 2026-11-12
AS43160 MalagaDatacenter
Registry name: ES-TEMPLUS-SPAIN TEMPLUS SPAIN SL, ES · PeeringDB
23IPv4 routes
100.0% RPKI valid · 30.4% with a route object
1IPv6 routes
100.0% RPKI valid · 100.0% with a route object
0RPKI invalid
0 origin · 0 maxLength
0No ROA
16 with no route object for this origin
0Low visibility
seen by under 10% of full-table peers
29Route objects not announced
registered with origin AS43160, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS43160, 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.158.80.0/24 | Valid | Nonecovered by 5.158.80.0/21 | 673 100% |
| 5.158.81.0/24 | Valid | Nonecovered by 5.158.80.0/21 | 673 100% |
| 5.158.83.0/24 | Valid | Nonecovered by 5.158.80.0/21 | 673 100% |
| 149.62.176.0/24 | Valid | Nonecovered by 149.62.176.0/22 | 673 100% |
| 149.62.177.0/24 | Valid | Nonecovered by 149.62.176.0/22 | 673 100% |
| 149.62.178.0/24 | Valid | Nonecovered by 149.62.176.0/22 | 673 100% |
| 149.62.179.0/24 | Valid | Nonecovered by 149.62.176.0/22 | 673 100% |
| 149.62.180.0/24 | Valid | Nonecovered by 149.62.180.0/22 | 673 100% |
| 149.62.181.0/24 | Valid | Nonecovered by 149.62.180.0/22 | 673 100% |
| 149.62.183.0/24 | Valid | Nonecovered by 149.62.180.0/22 | 673 100% |
| 37.235.32.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.33.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.34.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.35.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.36.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.39.0/24 | Valid | Nonecovered by 37.235.32.0/21 | 672 100% |
| 37.235.32.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 89.46.35.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 149.62.176.0/21 | Valid | RIR databaseRIPE | 673 100% |
| 149.62.182.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 149.100.10.0/23 | Valid | RIR databaseARIN | 673 100% |
| 149.100.19.0/24 | Valid | RIR databaseARIN | 673 100% |
| 154.54.220.0/24 | Valid | RIR databaseARIN | 673 100% |
| 2a01:b5c0::/32 | Valid | RIR databaseRIPE | 605 95% |
AS-SET
PeeringDB's irr_as_set for AS43160: AS-MDCDATACENTER-TRANSIT. 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 (AS43160 isn't in the set, or no route object for AS43160 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 | AS43160 in it | Not covered |
|---|---|---|---|---|---|
| AS-MDCDATACENTER-TRANSIT | RIPE1 member set in no database: AS-CISUR | 23 | 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 46 are in fix.csv.
- Route object: none16
- AS-SET: missing member1
- Route object: not announced29
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 5.158.80.0/24 | No route object for it. A route object for 5.158.80.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 5.158.81.0/24 | No route object for it. A route object for 5.158.80.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 5.158.83.0/24 | No route object for it. A route object for 5.158.80.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.176.0/24 | No route object for it. A route object for 149.62.176.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.177.0/24 | No route object for it. A route object for 149.62.176.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.178.0/24 | No route object for it. A route object for 149.62.176.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.179.0/24 | No route object for it. A route object for 149.62.176.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.180.0/24 | No route object for it. A route object for 149.62.180.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.181.0/24 | No route object for it. A route object for 149.62.180.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 149.62.183.0/24 | No route object for it. A route object for 149.62.180.0/22 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.32.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.33.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.34.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.35.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.36.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| Route object: none | 37.235.39.0/24 | No route object for it. A route object for 37.235.32.0/21 with origin AS43160 covers it (filters allowing more-specifics accept it). Add a route object with origin AS43160 in the RIR database for the space. |
| AS-SET: missing member | AS-MDCDATACENTER-TRANSIT | AS-MDCDATACENTER-TRANSIT (RIPE) lists AS-CISUR; no IRR database read has it. |
Route objects not announced
Route objects with origin AS43160 whose prefix no peer sees AS43160 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 5.40.32.0/23 | RIPE | Valid |
| 5.40.86.0/24 | RIPE | Valid |
| 5.40.128.0/24 | RIPE | Valid |
| 5.40.191.0/24 | RIPE | Valid |
| 5.40.252.0/24 | RIPE | Valid |
| 5.158.80.0/21 | RIPE | Valid |
| 5.158.86.0/24 | RIPE | Valid |
| 45.92.72.0/24 | RIPE | Invalid: origin |
| 45.92.73.0/24 | RIPE | Invalid: origin |
| 45.92.75.0/24 | RIPE | Invalid: origin |
| 62.82.84.0/24 | RIPE | Valid |
| 62.82.238.0/24 | RIPE | Valid |
| 62.175.202.0/24 | RIPE | Valid |
| 84.124.116.0/24 | RIPE | Valid |
| 89.140.40.0/23 | RIPE | Valid |
| 89.140.112.0/24 | RIPE | Valid |
| 89.140.120.0/24 | RIPE | Valid |
| 89.140.122.0/24 | RIPE | Valid |
| 89.140.197.0/24 | RIPE | Valid |
| 149.62.176.0/22 | RIPE | Invalid: maxLength |
| 149.62.180.0/22 | RIPE | Invalid: maxLength |
| 185.162.172.0/23 | RIPE | Invalid: origin |
| 185.162.172.0/24 | RIPE | Invalid: origin |
| 185.162.173.0/24 | RIPE | Invalid: origin |
| 185.174.212.0/24 | RIPE | Invalid: origin |
| 185.232.172.0/22 | RIPE | Invalid: origin |
| 185.240.164.0/24 | RIPE | Valid |
| 185.244.229.0/24 | RIPE | Invalid: origin |
| 185.244.230.0/24 | RIPE | 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.