Network · data from 2026-11-12
AS36436 InfoBunker
Registry name: INFOBUNKER - Infobunker, L.L.C., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS36436, 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.
| 204.138.27.0/24 | No ROA | Other origin only | 2 0%low visibility |
| 199.127.141.0/24 | Valid | Nonecovered by 199.127.136.0/21 | 673 100% |
| 2604:6800::/33 | Valid | Nonecovered by 2604:6800::/32 | 635 100% |
| 2604:6800:8000::/33 | Valid | Nonecovered by 2604:6800::/32 | 605 95% |
| 199.127.142.0/24 | Valid | Nonecovered by 199.127.136.0/21 | 3 0%low visibility |
| 162.247.128.0/24 | Valid | RIR databaseARIN | 671 100% |
| 162.247.129.0/24 | Valid | RIR databaseARIN | 671 100% |
| 162.247.130.0/23 | Valid | RIR databaseARIN | 671 100% |
| 199.115.204.0/22 | Valid | RIR databaseARIN | 671 100% |
| 199.127.136.0/21 | Valid | RIR databaseARIN | 671 100% |
| 208.71.32.0/22 | Valid | RIR databaseARIN | 671 100% |
| 208.95.0.0/22 | Valid | RIR databaseARIN | 671 100% |
| 2602:fed2:7111::/48 | Valid | RIR databaseARIN | 635 100% |
AS-SET
PeeringDB's irr_as_set for AS36436: AS36436:AS-IFB. 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 (AS36436 isn't in the set, or no route object for AS36436 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 | AS36436 in it | Not covered |
|---|---|---|---|---|---|
| AS36436:AS-IFB | ARIN | 7 | 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 8 are in fix.csv.
- ROA: none1
- Route object: none5
- Route object: not announced2
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: none | 204.138.27.0/24 | No ROA covers it. Add a ROA for AS36436, maxLength 24. |
| Route object: none | 204.138.27.0/24 | Route objects for it name AS21936. Add a route object with origin AS36436 in the RIR database for the space. |
| Route object: none | 199.127.141.0/24 | No route object for it. A route object for 199.127.136.0/21 with origin AS36436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36436 in the RIR database for the space. |
| Route object: none | 2604:6800::/33 | No route object for it. A route object for 2604:6800::/32 with origin AS36436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36436 in the RIR database for the space. |
| Route object: none | 2604:6800:8000::/33 | No route object for it. A route object for 2604:6800::/32 with origin AS36436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36436 in the RIR database for the space. |
| Route object: none | 199.127.142.0/24 | No route object for it. A route object for 199.127.136.0/21 with origin AS36436 covers it (filters allowing more-specifics accept it). Add a route object with origin AS36436 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS36436 whose prefix no peer sees AS36436 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 162.247.128.0/22 | ARIN | Valid |
| 2604:6800::/32 | ARIN | Valid |
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.