Network · data from 2026-11-12
AS270337 KT ENGENHARIA E COMPONENTES ELETRÔNICOS
Registry name: AS270337 - KT ENGENHARIA E COMPONENTES ELETRONICOS LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS270337, 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.
| 2804:6a74:6800::/38 | Valid | Nonecovered by 2804:6a74::/33 | 633 100% |
| 190.83.50.0/23 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 190.83.48.0/23 | Valid | Other IRR onlyRADB, TC | 666 99% |
| 190.83.48.0/24 | Valid | Other IRR onlyRADB, TC | 665 99% |
| 190.83.49.0/24 | Valid | Other IRR onlyRADB, TC | 665 99% |
| 2804:6a74::/33 | Valid | Other IRR onlyRADB | 633 100% |
| 2804:6a74:8000::/33 | Valid | Other IRR onlyRADB | 633 100% |
AS-SET
PeeringDB's irr_as_set for AS270337: TC::AS270337. 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 (AS270337 isn't in the set, or no route object for AS270337 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 | AS270337 in it | Not covered | |
|---|---|---|---|---|---|---|
| TC::AS270337 | A single AS number, not a set: AS270337 (this network), 10 route objects. | |||||
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 11 are in fix.csv.
- Route object: none1
- Route object: RIR6
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 2804:6a74:6800::/38 | No route object for it. A route object for 2804:6a74::/33 with origin AS270337 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270337 in the RIR database for the space. |
| Route object: RIR | 190.83.50.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.83.48.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.83.48.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 190.83.49.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6a74::/33 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 2804:6a74:8000::/33 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS270337 whose prefix no peer sees AS270337 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 190.83.48.0/22 | RADB, TC | Valid |
| 190.83.50.0/24 | RADB, TC | Valid |
| 190.83.51.0/24 | RADB, TC | Valid |
| 2804:6a74::/32 | RADB, TC | 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.