Network · data from 2026-11-12
AS267345 BOM JESUS NET LTDA
Registry name: AS267345 - BOM JESUS NET LTDA, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS267345, 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.
| 167.250.245.0/24 | No ROA | Other origin only | 672 100% |
| 45.234.80.0/22 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.234.80.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.234.82.0/23 | Valid | Other IRR onlyRADB, TC | 672 100% |
| 45.234.80.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.234.81.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.234.82.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 45.234.83.0/24 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:4c0c::/32 | Valid | Other IRR onlyRADB, TC | 632 99% |
AS-SET
PeeringDB's irr_as_set for AS267345: AS267345. 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 (AS267345 isn't in the set, or no route object for AS267345 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 | AS267345 in it | Not covered | |
|---|---|---|---|---|---|---|
| AS267345 | A single AS number, not a set: AS267345 (this network), 15 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 17 are in fix.csv.
- ROA: none1
- Route object: none1
- Route object: RIR8
- Route object: not announced7
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 167.250.245.0/24 | No ROA covers it. Add a ROA for AS267345, maxLength 24. |
| Route object: none | 167.250.245.0/24 | Route objects for it name AS265238. Add a route object with origin AS267345 in the RIR database for the space. |
| Route object: RIR | 45.234.80.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.80.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.82.0/23 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.80.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.81.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.82.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 45.234.83.0/24 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:4c0c::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
Route objects not announced
Route objects with origin AS267345 whose prefix no peer sees AS267345 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2804:4c0c::/33 | TC | Valid |
| 2804:4c0c::/34 | TC | Valid |
| 2804:4c0c:4000::/34 | TC | Valid |
| 2804:4c0c:8000::/33 | TC | Valid |
| 2804:4c0c:8000::/34 | TC | Valid |
| 2804:4c0c:c000::/34 | TC | Valid |
| 2804:52d4::/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.