Network · data from 2026-11-12
AS13316 SES Sistemas Electrónicos S.A.
Registry name: AS13316 - SES Sistemas Electronicos S.A., AR · PeeringDB
30IPv4 routes
100.0% RPKI valid · 16.7% with a route object
0IPv6 routes
0RPKI invalid
0 origin · 0 maxLength
0No ROA
25 with no route object for this origin
1Low visibility
seen by under 10% of full-table peers
0Route objects not announced
registered with origin AS13316, seen from no peer
Announced routes
Every prefix a peer of the route collectors sees with origin AS13316, 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.
| 190.103.0.0/24 | Valid | Nonecovered by 190.103.0.0/22 | 669 99% |
| 190.103.1.0/24 | Valid | Nonecovered by 190.103.0.0/22 | 669 99% |
| 190.103.2.0/24 | Valid | Nonecovered by 190.103.0.0/22 | 669 99% |
| 190.103.3.0/24 | Valid | Nonecovered by 190.103.0.0/22 | 669 99% |
| 190.103.4.0/24 | Valid | Nonecovered by 190.103.4.0/22 | 669 99% |
| 190.103.5.0/24 | Valid | Nonecovered by 190.103.4.0/22 | 669 99% |
| 190.103.6.0/24 | Valid | Nonecovered by 190.103.4.0/22 | 669 99% |
| 190.103.7.0/24 | Valid | Nonecovered by 190.103.4.0/22 | 669 99% |
| 190.103.8.0/24 | Valid | Nonecovered by 190.103.8.0/22 | 669 99% |
| 190.103.9.0/24 | Valid | Nonecovered by 190.103.8.0/22 | 669 99% |
| 190.103.10.0/24 | Valid | Nonecovered by 190.103.8.0/22 | 669 99% |
| 190.103.11.0/24 | Valid | Nonecovered by 190.103.8.0/22 | 669 99% |
| 190.103.12.0/24 | Valid | Nonecovered by 190.103.12.0/22 | 669 99% |
| 190.103.13.0/24 | Valid | Nonecovered by 190.103.12.0/22 | 669 99% |
| 190.103.14.0/24 | Valid | Nonecovered by 190.103.12.0/22 | 669 99% |
| 190.103.15.0/24 | Valid | Nonecovered by 190.103.12.0/22 | 669 99% |
| 200.11.112.0/22 | Valid | None | 669 99% |
| 200.11.112.0/24 | Valid | None | 669 99% |
| 200.11.113.0/24 | Valid | None | 669 99% |
| 200.11.114.0/24 | Valid | None | 669 99% |
| 200.11.115.0/24 | Valid | None | 669 99% |
| 200.11.116.0/24 | Valid | Nonecovered by 200.11.116.0/22 | 669 99% |
| 200.11.117.0/24 | Valid | Nonecovered by 200.11.116.0/22 | 669 99% |
| 200.11.118.0/24 | Valid | Nonecovered by 200.11.116.0/22 | 669 99% |
| 200.11.119.0/24 | Valid | Nonecovered by 200.11.116.0/22 | 8 1%low visibility |
| 190.103.4.0/22 | Valid | Other IRR onlyRADB | 669 99% |
| 190.103.0.0/22 | Valid | Other IRR onlyRADB | 665 99% |
| 190.103.8.0/22 | Valid | Other IRR onlyRADB | 665 99% |
| 190.103.12.0/22 | Valid | Other IRR onlyRADB | 665 99% |
| 200.11.116.0/22 | Valid | Other IRR onlyRADB | 665 99% |
AS-SET
PeeringDB's irr_as_set for AS13316: AS13316:AS-CUSTOMERS. 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 (AS13316 isn't in the set, or no route object for AS13316 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 | AS13316 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS13316:AS-CUSTOMERS | In no IRR database read today. | |||||
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 31 are in fix.csv.
- Route object: none25
- Route object: RIR5
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 190.103.0.0/24 | No route object for it. A route object for 190.103.0.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.1.0/24 | No route object for it. A route object for 190.103.0.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.2.0/24 | No route object for it. A route object for 190.103.0.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.3.0/24 | No route object for it. A route object for 190.103.0.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.4.0/24 | No route object for it. A route object for 190.103.4.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.5.0/24 | No route object for it. A route object for 190.103.4.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.6.0/24 | No route object for it. A route object for 190.103.4.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.7.0/24 | No route object for it. A route object for 190.103.4.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.8.0/24 | No route object for it. A route object for 190.103.8.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.9.0/24 | No route object for it. A route object for 190.103.8.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.10.0/24 | No route object for it. A route object for 190.103.8.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.11.0/24 | No route object for it. A route object for 190.103.8.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.12.0/24 | No route object for it. A route object for 190.103.12.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.13.0/24 | No route object for it. A route object for 190.103.12.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.14.0/24 | No route object for it. A route object for 190.103.12.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 190.103.15.0/24 | No route object for it. A route object for 190.103.12.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.112.0/22 | No route object for it. Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.112.0/24 | No route object for it. Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.113.0/24 | No route object for it. Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.114.0/24 | No route object for it. Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.115.0/24 | No route object for it. Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.116.0/24 | No route object for it. A route object for 200.11.116.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.117.0/24 | No route object for it. A route object for 200.11.116.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.118.0/24 | No route object for it. A route object for 200.11.116.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: none | 200.11.119.0/24 | No route object for it. A route object for 200.11.116.0/22 with origin AS13316 covers it (filters allowing more-specifics accept it). Add a route object with origin AS13316 in the RIR database for the space. |
| Route object: RIR | 190.103.4.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.103.0.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.103.8.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 190.103.12.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 200.11.116.0/22 | Route object only in RADB. Add it in the RIR database for the space. |
| AS-SET: not found | AS13316:AS-CUSTOMERS | PeeringDB names AS13316:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Every route object with origin AS13316 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.