Network · data from 2026-11-12
AS265036 BMJNET TELECOM
Registry name: AS265036 - BMJnet Telecom, BR · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS265036, 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.
| 170.150.226.0/23 | Valid | Nonecovered by 170.150.224.0/22 | 671 100% |
| 170.150.224.0/23 | Valid | Nonecovered by 170.150.224.0/22 | 670 100% |
| 2804:31c4:8000::/33 | Valid | Nonecovered by 2804:31c4::/32 | 633 100% |
| 2804:31c4::/33 | Valid | Nonecovered by 2804:31c4::/32 | 632 99% |
| 2804:31c4::/34 | Valid | Nonecovered by 2804:31c4::/32 | 6 1%low visibility |
| 170.150.224.0/24 | Valid | Nonecovered by 170.150.224.0/22 | 1 0%low visibility |
| 170.150.225.0/24 | Valid | Nonecovered by 170.150.224.0/22 | 1 0%low visibility |
| 170.150.226.0/24 | Valid | Nonecovered by 170.150.224.0/22 | 1 0%low visibility |
| 170.150.227.0/24 | Valid | Nonecovered by 170.150.224.0/22 | 1 0%low visibility |
| 170.150.224.0/22 | Valid | Other IRR onlyRADB, TC | 671 100% |
| 2804:31c4::/32 | Valid | Other IRR onlyRADB, TC | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS265036: AS-AS265036. 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 (AS265036 isn't in the set, or no route object for AS265036 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 | AS265036 in it | Not covered |
|---|---|---|---|---|---|
| AS-AS265036 | RADBlists itself further down2 member sets in no database: AS265036:AS-ALL, AS272733:AS-ALL | 75 | 18 | 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 13 are in fix.csv.
- Route object: none9
- Route object: RIR2
- AS-SET: missing member2
| Change | Prefix or set | Detail |
|---|---|---|
| Route object: none | 170.150.226.0/23 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 170.150.224.0/23 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 2804:31c4:8000::/33 | No route object for it. A route object for 2804:31c4::/32 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 2804:31c4::/33 | No route object for it. A route object for 2804:31c4::/32 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 2804:31c4::/34 | No route object for it. A route object for 2804:31c4::/32 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 170.150.224.0/24 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 170.150.225.0/24 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 170.150.226.0/24 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: none | 170.150.227.0/24 | No route object for it. A route object for 170.150.224.0/22 with origin AS265036 covers it (filters allowing more-specifics accept it). Add a route object with origin AS265036 in the RIR database for the space. |
| Route object: RIR | 170.150.224.0/22 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| Route object: RIR | 2804:31c4::/32 | Route object only in RADB, TC. Add it in the RIR database for the space. |
| AS-SET: missing member | AS-AS265036 | AS-AS265036 (RADB) lists AS265036:AS-ALL; no IRR database read has it. |
| AS-SET: missing member | AS-AS265036 | AS-AS265036 (RADB) lists AS272733:AS-ALL; no IRR database read has it. |
Route objects not announced
Every route object with origin AS265036 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.