bgpreport

Network · data from 2026-11-12

AS400696 MIBURA-1

Registry name: MIBURA-1 - MIBURA, INC., US · PeeringDB

23IPv4 routes 100.0% RPKI valid · 100.0% with a route object
19IPv6 routes 89.5% RPKI valid · 52.6% with a route object
2RPKI invalid 2 origin · 0 maxLength
0No ROA 9 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
5Route objects not announced registered with origin AS400696, seen from no peer

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 11
2a02:9010:bc::/48 Invalid: origin None 2 0%low visibility 2
2602:f6e9:4::/48 Valid Nonecovered by 2602:f6e9::/40 636 100% 67
2602:f6e9:5::/48 Valid Nonecovered by 2602:f6e9::/40 636 100% 67
2602:f6e9:8::/48 Valid Nonecovered by 2602:f6e9::/40 636 100% 69
2602:f6e9:9::/48 Valid Nonecovered by 2602:f6e9::/40 636 100% 67
2602:f6e9:1::/48 Valid Nonecovered by 2602:f6e9::/40 635 100% 69
2602:f6e9::/48 Valid Nonecovered by 2602:f6e9::/40 634 100% 68
2602:f6e9:7::/48 Valid Nonecovered by 2602:f6e9::/40 634 100% 68
66.56.83.0/24 Valid RIR databaseRIPE 673 100% 67
89.33.14.0/24 Valid RIR databaseRIPE 673 100% 67
124.198.134.0/24 Valid RIR databaseRIPE 673 100% 67
158.173.39.0/24 Valid RIR databaseRIPE 673 100% 66
31.58.159.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
46.244.98.0/24 Valid RIR databaseRIPE 672 100% 67
85.203.19.0/24 Valid RIR databaseRIPE 672 100% 67
155.2.193.0/24 Valid RIR databaseRIPE 672 100% 68
158.173.35.0/24 Valid RIR databaseRIPE 672 100% 67
45.8.26.0/24 Valid RIR databaseRIPE 671 100% 67
45.95.240.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
45.133.0.0/24 Valid RIR databaseRIPE 671 100% 67
45.152.148.0/24 Valid RIR databaseRIPE 671 100% 67
92.240.148.0/24 Valid RIR databaseRIPE 671 100% 68
103.138.78.0/24 Valid RIR databaseRIPE 671 100% 67
155.2.220.0/24 Valid RIR databaseRIPE 671 100% 69
158.173.145.0/24 Valid RIR databaseRIPE 671 100% 68
158.173.38.0/24 Valid RIR databaseRIPE 670 100% 67
185.102.168.0/24 Valid RIR databaseRIPE 670 100% 67
45.84.214.0/24 Valid RIR databaseRIPE 669 99% 67
45.94.30.0/24 Valid RIR databaseRIPE 669 99% 67
45.130.142.0/24 Valid RIR databaseRIPE 669 99% 67
2a0f:15c0::/32 Valid RIR databaseRIPE 636 100% 67
2a0f:15c5::/32 Valid RIR databaseRIPE 636 100% 67
2a0f:15c7::/32 Valid RIR databaseRIPE 636 100% 67
2a0f:15c2::/32 Valid RIR databaseRIPE 635 100% 69
2a0f:15c4::/32 Valid RIR databaseRIPE 635 100% 67
2602:f6e9:2::/48 Valid RIR databaseARIN 634 100% 69
2a11:f880::/32 Valid RIR databaseRIPE 634 100% 67
2a0f:15c6::/32 Valid RIR databaseRIPE 632 99% 67
2a10:5e80::/48 Valid RIR databaseRIPE 631 99% 67
2a10:5e80:1::/48 Valid RIR databaseRIPE 631 99% 67
45.94.29.0/24 Valid RIR databaseRIPE 2 0%low visibility 2

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
ChangePrefix or setDetailFull-table peers
ROA: origin2001:c20:48d8::/48ROAs covering it name AS3758, AS9255, not AS400696. If AS400696 should announce it, add a ROA for AS400696.19 of 636
Route object: none2001:c20:48d8::/48Route objects for it name AS9255. Add a route object with origin AS400696 in the RIR database for the space.19 of 636
ROA: origin2a02:9010:bc::/48ROAs covering it name AS3352, not AS400696. If AS400696 should announce it, add a ROA for AS400696.2 of 636
Route object: none2a02:9010:bc::/48No route object for it. Add a route object with origin AS400696 in the RIR database for the space.2 of 636
Route object: none2602:f6e9:4::/48No 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.636 of 636
Route object: none2602:f6e9:5::/48No 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.636 of 636
Route object: none2602:f6e9:8::/48No 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.636 of 636
Route object: none2602:f6e9:9::/48No 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.636 of 636
Route object: none2602:f6e9:1::/48No 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.635 of 636
Route object: none2602:f6e9::/48No 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.634 of 636
Route object: none2602:f6e9:7::/48No 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.634 of 636

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::/40ARINValid
2a07:bdc2::/32RIPEValid
2a0f:15c3::/32RIPEValid
2a10:5e80::/32RIPEValid
2a10:7405::/32RIPEValid

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.