bgpreport

Network · data from 2026-11-12

AS26286 MYSTICDEVIO - MysticDev LLC

Registry name: MYSTICDEVIO - MysticDev LLC, US · not in PeeringDB

9IPv4 routes 77.8% RPKI valid · 88.9% with a route object
6IPv6 routes 83.3% RPKI valid · 50.0% with a route object
2RPKI invalid 2 origin · 0 maxLength
1No ROA 4 with no route object for this origin
2Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS26286, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS26286, 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.
2602:fbdf::/48 Invalid: origin Other origin only 9 1%low visibility 11
64.112.124.0/24 Invalid: origin Other origin only 5 1%low visibility 5
204.197.170.0/24 No ROA RIR databaseARIN 671 100% 67
2602:f992:f6::/48 Valid None 634 100% 67
2602:f992:f8::/48 Valid None 634 100% 67
23.137.132.0/24 Valid RIR databaseARIN 671 100% 67
23.138.156.0/24 Valid RIR databaseARIN 671 100% 67
104.167.241.0/24 Valid RIR databaseARIN 671 100% 67
104.167.242.0/24 Valid RIR databaseARIN 671 100% 67
144.225.120.0/24 Valid RIR databaseARIN, RADB 671 100% 67
192.147.25.0/24 Valid RIR databaseARIN 671 100% 67
216.75.83.0/24 Valid RIR databaseARIN, RADB 671 100% 67
2602:f661::/40 Valid RIR databaseARIN 634 100% 69
2602:f689:10::/44 Valid RIR databaseARIN 634 100% 69
2602:fccf::/37 Valid RIR databaseARIN 634 100% 69

AS-SET

AS26286 isn't in PeeringDB, where networks name their 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 7 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none4
ChangePrefix or setDetailFull-table peers
ROA: origin2602:fbdf::/48ROAs covering it name AS401104, not AS26286. If AS26286 should announce it, add a ROA for AS26286.9 of 636
Route object: none2602:fbdf::/48Route objects for it name AS401104. Add a route object with origin AS26286 in the RIR database for the space.9 of 636
ROA: origin64.112.124.0/24ROAs covering it name AS214640, not AS26286. If AS26286 should announce it, add a ROA for AS26286.5 of 673
Route object: none64.112.124.0/24Route objects for it name AS214640, AS398355. Add a route object with origin AS26286 in the RIR database for the space.5 of 673
ROA: none204.197.170.0/24No ROA covers it. Add a ROA for AS26286, maxLength 24.671 of 673
Route object: none2602:f992:f6::/48No route object for it. Add a route object with origin AS26286 in the RIR database for the space.634 of 636
Route object: none2602:f992:f8::/48No route object for it. Add a route object with origin AS26286 in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS26286 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.