Network · data from 2026-11-12
AS269137 PNTI
Registry name: AS269137 - PNTI - Ponto Net Tecnologia em internet, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS269137, 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.180.145.0/24 | Valid | Nonecovered by 45.180.144.0/22 | 673 100% |
| 45.180.147.0/24 | Valid | Nonecovered by 45.180.144.0/22 | 673 100% |
| 45.180.144.0/24 | Valid | Nonecovered by 45.180.144.0/22 | 672 100% |
| 45.180.146.0/24 | Valid | Nonecovered by 45.180.144.0/22 | 672 100% |
| 45.180.144.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 2804:5ff8::/32 | Valid | Other IRR onlyRADB, TC | 634 100% |
AS-SET
PeeringDB's irr_as_set for AS269137: AS-PNTI. 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 (AS269137 isn't in the set, or no route object for AS269137 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 | AS269137 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS-PNTI | 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 7 are in fix.csv.
- Route object: none4
- Route object: RIR2
- AS-SET: not found1
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 45.180.145.0/24 | No route object for it. A route object for 45.180.144.0/22 with origin AS269137 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269137 in the RIR database for the space. |
| Route object: none | 45.180.147.0/24 | No route object for it. A route object for 45.180.144.0/22 with origin AS269137 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269137 in the RIR database for the space. |
| Route object: none | 45.180.144.0/24 | No route object for it. A route object for 45.180.144.0/22 with origin AS269137 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269137 in the RIR database for the space. |
| Route object: none | 45.180.146.0/24 | No route object for it. A route object for 45.180.144.0/22 with origin AS269137 covers it (filters allowing more-specifics accept it). Add a route object with origin AS269137 in the RIR database for the space. |
| Route object: RIR | 45.180.144.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:5ff8::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: not found | AS-PNTI | PeeringDB names AS-PNTI; no IRR database read has it. |
Route objects not announced
Every route object with origin AS269137 is announced.
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.