Network · data from 2026-11-12
AS400696 MIBURA-1
Registry name: MIBURA-1 - MIBURA, INC., US · PeeringDB
Announced routes
Every prefix a peer of the route collectors sees with origin AS400696, 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.
| 2001:c20:48d8::/48 | Invalid: origin | Other origin only | 19 3%low visibility |
| 2a02:9010:bc::/48 | Invalid: origin | None | 2 0%low visibility |
| 2602:f6e9:4::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 636 100% |
| 2602:f6e9:5::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 636 100% |
| 2602:f6e9:8::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 636 100% |
| 2602:f6e9:9::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 636 100% |
| 2602:f6e9:1::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 635 100% |
| 2602:f6e9::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 634 100% |
| 2602:f6e9:7::/48 | Valid | Nonecovered by 2602:f6e9::/40 | 634 100% |
| 66.56.83.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 89.33.14.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 124.198.134.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 158.173.39.0/24 | Valid | RIR databaseRIPE | 673 100% |
| 31.58.159.0/24 | Valid | RIR databaseRADB, RIPE | 672 100% |
| 46.244.98.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 85.203.19.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 155.2.193.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 158.173.35.0/24 | Valid | RIR databaseRIPE | 672 100% |
| 45.8.26.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.95.240.0/24 | Valid | RIR databaseRADB, RIPE | 671 100% |
| 45.133.0.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 45.152.148.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 92.240.148.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 103.138.78.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 155.2.220.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 158.173.145.0/24 | Valid | RIR databaseRIPE | 671 100% |
| 158.173.38.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 185.102.168.0/24 | Valid | RIR databaseRIPE | 670 100% |
| 45.84.214.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.94.30.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 45.130.142.0/24 | Valid | RIR databaseRIPE | 669 99% |
| 2a0f:15c0::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0f:15c5::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0f:15c7::/32 | Valid | RIR databaseRIPE | 636 100% |
| 2a0f:15c2::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2a0f:15c4::/32 | Valid | RIR databaseRIPE | 635 100% |
| 2602:f6e9:2::/48 | Valid | RIR databaseARIN | 634 100% |
| 2a11:f880::/32 | Valid | RIR databaseRIPE | 634 100% |
| 2a0f:15c6::/32 | Valid | RIR databaseRIPE | 632 99% |
| 2a10:5e80::/48 | Valid | RIR databaseRIPE | 631 99% |
| 2a10:5e80:1::/48 | Valid | RIR databaseRIPE | 631 99% |
| 45.94.29.0/24 | Valid | RIR databaseRIPE | 2 0%low visibility |
AS-SET
AS400696's PeeringDB record names no AS-SET.
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 16 are in fix.csv.
- ROA: origin2
- Route object: none9
- Route object: not announced5
| Change | Prefix or set | Detail |
|---|---|---|
| ROA: origin | 2001:c20:48d8::/48 | ROAs covering it name AS3758, AS9255, not AS400696. If AS400696 should announce it, add a ROA for AS400696. |
| Route object: none | 2001:c20:48d8::/48 | Route objects for it name AS9255. Add a route object with origin AS400696 in the RIR database for the space. |
| ROA: origin | 2a02:9010:bc::/48 | ROAs covering it name AS3352, not AS400696. If AS400696 should announce it, add a ROA for AS400696. |
| Route object: none | 2a02:9010:bc::/48 | No route object for it. Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:4::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:5::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:8::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:9::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:1::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
| Route object: none | 2602:f6e9:7::/48 | No route object for it. A route object for 2602:f6e9::/40 with origin AS400696 covers it (filters allowing more-specifics accept it). Add a route object with origin AS400696 in the RIR database for the space. |
Route objects not announced
Route objects with origin AS400696 whose prefix no peer sees AS400696 announce. Many are kept on purpose (backup routes, space announced only in some places).
| 2602:f6e9::/40 | ARIN | Valid |
| 2a07:bdc2::/32 | RIPE | Valid |
| 2a0f:15c3::/32 | RIPE | Valid |
| 2a10:5e80::/32 | RIPE | Valid |
| 2a10:7405::/32 | RIPE | 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.