Network · data from 2026-11-12
AS269537 MUNDO TELECOM E SERVICOS LTDA - EPP
Registry name: AS269537 - MUNDO TELECOM E SERVICOS LTDA - EPP, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269537, 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:83c4:600::/44 | Invalid: origin | Other origin only | 18 3%low visibility |
| 45.188.169.0/24 | Valid | Other IRR onlyRADB | 672 100% |
| 45.188.170.0/24 | Valid | Other IRR onlyRADB | 671 100% |
| 45.188.168.0/24 | Valid | Other IRR onlyRADB | 667 99% |
| 45.188.171.0/24 | Valid | Other IRR onlyRADB | 667 99% |
AS-SET
PeeringDB's irr_as_set for AS269537: AS-MUNDOTELECOM. 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 (AS269537 isn't in the set, or no route object for AS269537 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 | AS269537 in it | Not covered |
|---|---|---|---|---|---|
| AS-MUNDOTELECOM | RADB | 1 | 1 | Yes | 1 |
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 10 are in fix.csv.
- ROA: origin1
- Route object: none1
- Route object: RIR4
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2804:83c4:600::/44 | ROAs covering it name AS272218, not AS269537. If AS269537 should announce it, add a ROA for AS269537. |
| Route object: none | 2804:83c4:600::/44 | Route objects for it name AS272218. Add a route object with origin AS269537 in the RIR database for the space. |
| Route object: RIR | 45.188.169.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.170.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.168.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
| Route object: RIR | 45.188.171.0/24 | Route object only in RADB. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS269537 whose prefix no peer sees AS269537 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.188.168.0/22 | RADB | No ROA |
| 45.188.168.0/23 | RADB | No ROA |
| 45.188.170.0/23 | RADB | No ROA |
| 2804:6624::/32 | RADB | 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.