Network · data from 2026-11-12
AS57365 Numintec Comunicaciones
Registry name: Numintec Numintec Comunicaciones S.L., ES · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS57365, 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.
| 128.140.204.0/24 | Invalid: maxLength | Nonecovered by 128.140.200.0/21 | 6 1%low visibility |
| 128.140.200.0/24 | Valid | Nonecovered by 128.140.200.0/21 | 673 100% |
| 128.140.201.0/24 | Valid | Nonecovered by 128.140.200.0/21 | 672 100% |
| 128.140.200.0/21 | Valid | RIR databaseRIPE | 671 100% |
AS-SET
PeeringDB's irr_as_set for AS57365: AS-NUMINTEC. 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 (AS57365 isn't in the set, or no route object for AS57365 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 | AS57365 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-NUMINTEC | 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 6 are in fix.csv.
- ROA: maxLength1
- Route object: none3
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: maxLength | 128.140.204.0/24 | ROA 128.140.200.0/21 AS57365 has maxLength 21; the route is a /24. Raise the maxLength, or add a ROA for 128.140.204.0/24. |
| Route object: none | 128.140.204.0/24 | No route object for it. A route object for 128.140.200.0/21 with origin AS57365 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57365 in the RIR database for the space. |
| Route object: none | 128.140.200.0/24 | No route object for it. A route object for 128.140.200.0/21 with origin AS57365 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57365 in the RIR database for the space. |
| Route object: none | 128.140.201.0/24 | No route object for it. A route object for 128.140.200.0/21 with origin AS57365 covers it (filters allowing more-specifics accept it). Add a route object with origin AS57365 in the RIR database for the space. |
| AS-SET: not found | AS-NUMINTEC | PeeringDB names AS-NUMINTEC; no IRR database read has it. |
Route objects not announced
Route objects with origin AS57365 whose prefix no peer sees AS57365 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2a03:9580::/32 | 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.