Network · data from 2026-11-12
AS269175 SECRETARIA MUNICIPAL DE PLANEJAMENTO ORCAMENTO E G
Registry name: AS269175 - SECRETARIA MUNICIPAL DE PLANEJAMENTO ORCAMENTO E G, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269175, 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.181.94.0/24 | Valid | Other IRR onlyTC | 671 100% |
| 45.181.95.0/24 | Valid | Other IRR onlyTC | 669 99% |
| 45.181.92.0/24 | Valid | Other IRR onlyTC | 668 99% |
| 45.181.93.0/24 | Valid | Other IRR onlyTC | 667 99% |
| 2804:1f4c:8000::/33 | Valid | Other IRR onlyTC | 635 100% |
| 2804:1f4c::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
| 2804:1f4c::/33 | Valid | Other IRR onlyTC | 630 99% |
AS-SET
PeeringDB's irr_as_set for AS269175: AS269175:AS-UPSTREAMS. 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 (AS269175 isn't in the set, or no route object for AS269175 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 | AS269175 in it | Not covered |
|---|---|---|---|---|---|
| AS269175:AS-UPSTREAMS | TC | 3 | 1 | No | 7 |
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 12 are in fix.csv.
- Route object: RIR7
- AS-SET: own ASN1
- Route object: not announced4
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: RIR | 45.181.94.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.95.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.92.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.181.93.0/24 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1f4c:8000::/33 | Route object only in TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1f4c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:1f4c::/33 | Route object only in TC. Add it in the RIR database for the space. |
| AS-SET: own ASN | AS269175:AS-UPSTREAMS | AS269175 isn't in AS269175:AS-UPSTREAMS (TC) once expanded. Add AS269175 to it. |
Route objects not announced
Route objects with origin AS269175 whose prefix no peer sees AS269175 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 45.181.92.0/22 | RADB, TC | Valid |
| 45.181.92.0/23 | RADB, TC | Valid |
| 45.181.94.0/23 | RADB, TC | Valid |
| 2801:80:3690::/48 | 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.