Network · data from 2026-11-12
AS272018 KM TECHNOLOGY
Registry name: AS272018 - KM TECHNOLOGY, C.A., VE · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS272018, 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.
| 154.95.54.0/24 | Valid | Other origin onlycovered by 154.95.54.0/23 | 666 99% |
| 154.95.55.0/24 | Valid | Other origin onlycovered by 154.95.54.0/23 | 666 99% |
| 45.198.56.0/24 | Valid | Nonecovered by 45.198.56.0/23 | 665 99% |
| 45.198.57.0/24 | Valid | Nonecovered by 45.198.56.0/23 | 665 99% |
| 2803:4510::/33 | Valid | Nonecovered by 2803:4510::/32 | 631 99% |
| 2803:4510:8000::/33 | Valid | Nonecovered by 2803:4510::/32 | 631 99% |
| 154.95.54.0/23 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 156.235.90.0/24 | Valid | RIR databaseAFRINIC, RADB | 669 99% |
| 45.198.56.0/23 | Valid | RIR databaseAFRINIC, RADB | 666 99% |
| 156.235.91.0/24 | Valid | RIR databaseAFRINIC, RADB | 666 99% |
AS-SET
PeeringDB's irr_as_set for AS272018: AS272018: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 (AS272018 isn't in the set, or no route object for AS272018 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 | AS272018 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS272018: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 8 are in fix.csv.
- Route object: none6
- AS-SET: not found1
- Route object: not announced1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 154.95.54.0/24 | Route objects for it name AS17561. A route object for 154.95.54.0/23 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| Route object: none | 154.95.55.0/24 | Route objects for it name AS17561. A route object for 154.95.54.0/23 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| Route object: none | 45.198.56.0/24 | No route object for it. A route object for 45.198.56.0/23 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| Route object: none | 45.198.57.0/24 | No route object for it. A route object for 45.198.56.0/23 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| Route object: none | 2803:4510::/33 | No route object for it. A route object for 2803:4510::/32 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| Route object: none | 2803:4510:8000::/33 | No route object for it. A route object for 2803:4510::/32 with origin AS272018 covers it (filters allowing more-specifics accept it). Add a route object with origin AS272018 in the RIR database for the space. |
| AS-SET: not found | AS272018:AS-CUSTOMERS | PeeringDB names AS272018:AS-CUSTOMERS; no IRR database read has it. |
Route objects not announced
Route objects with origin AS272018 whose prefix no peer sees AS272018 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2803:4510::/32 | RADB | Valid |
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.