bgpreport

Network · data from 2026-11-12

AS200658 CoreCloud

Registry name: CoreCloud CoreCloud Systems Ltd, GB · PeeringDB

12IPv4 routes 75.0% RPKI valid · 83.3% with a route object
0IPv6 routes
2RPKI invalid 2 origin · 0 maxLength
1No ROA 2 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
2Route objects not announced registered with origin AS200658, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS200658, 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.
136.175.80.0/24 Invalid: origin None 4 1%low visibility 3
141.195.127.0/24 Invalid: origin Other origin only 2 0%low visibility 2
216.205.156.0/24 No ROA RIR databaseARIN 668 99% 67
31.207.6.0/24 Valid RIR databaseRIPE 668 99% 67
64.205.102.0/24 Valid RIR databaseARIN, RADB 668 99% 67
87.232.74.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
104.143.192.0/24 Valid RIR databaseRIPE 668 99% 67
134.195.8.0/24 Valid RIR databaseARIN 668 99% 67
134.195.9.0/24 Valid RIR databaseARIN 668 99% 67
212.66.55.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
72.35.245.0/24 Valid RIR databaseRIPE 667 99% 67
154.13.128.0/24 Valid RIR databaseARIN 2 0%low visibility 2

AS-SET

AS200658'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 7 are in fix.csv.

  • ROA: origin2
  • ROA: none1
  • Route object: none2
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: origin136.175.80.0/24An AS0 ROA covers it (the holder's statement that it shouldn't be routed). If AS200658 should announce it, add a ROA for AS200658.4 of 673
Route object: none136.175.80.0/24No route object for it. Add a route object with origin AS200658 in the RIR database for the space.4 of 673
ROA: origin141.195.127.0/24ROAs covering it name AS400384, not AS200658. If AS200658 should announce it, add a ROA for AS200658.2 of 673
Route object: none141.195.127.0/24Route objects for it name AS400384. Add a route object with origin AS200658 in the RIR database for the space.2 of 673
ROA: none216.205.156.0/24No ROA covers it. Add a ROA for AS200658, maxLength 24.668 of 673

Route objects not announced

Route objects with origin AS200658 whose prefix no peer sees AS200658 announce. Many are kept on purpose (backup routes, space announced only in some places).

142.249.25.0/24ARINInvalid: origin
2a0c:9a40:8930::/48RIPEValid

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.