Network · data from 2026-11-12
AS269276 WIT SERVICOS DE TELECOMUNICACÕES
Registry name: AS269276 - WIT SERVICOS DE TELECOMUNICACOES LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269276, 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.
| 45.182.88.0/23 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 45.182.90.0/24 | Valid | Other IRR onlyRADB, TC | 669 99% |
| 2804:621c::/32 | Valid | Other IRR onlyALTDB, RADB, TC | 636 100% |
| 45.182.91.0/24 | Valid | Other IRR onlyTC | 2 0%low visibility |
AS-SET
PeeringDB's irr_as_set for AS269276: AS269276:AS-WITTELECOM. 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 (AS269276 isn't in the set, or no route object for AS269276 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 | AS269276 in it | Not covered |
|---|---|---|---|---|---|
| AS269276:AS-WITTELECOM | TC | 1 | 3 | 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 15 are in fix.csv.
- Route object: RIR4
- Route object: not announced11
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.182.88.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.182.90.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:621c::/32 | Route object only in ALTDB, RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.182.91.0/24 | Route object only in TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269276 whose prefix no peer sees AS269276 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.182.88.0/22 | RADB, TC | No ROA |
| 45.182.90.0/23 | RADB, TC | No ROA |
| 187.111.120.0/22 | ALTDB | No ROA |
| 187.111.120.0/23 | ALTDB | No ROA |
| 192.141.224.0/22 | ALTDB | No ROA |
| 192.141.224.0/24 | ALTDB | No ROA |
| 192.141.225.0/24 | ALTDB | No ROA |
| 192.141.226.0/24 | ALTDB | No ROA |
| 192.141.227.0/24 | ALTDB | No ROA |
| 2804:4228::/32 | ALTDB | No ROA |
| 2804:7f20::/32 | ALTDB | 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.