bgpreport

Network · data from 2026-11-12

AS1405 Caelus Technology

Registry name: CAELUS-AS - Caelus Technology LLC, US · PeeringDB

19IPv4 routes 89.5% RPKI valid · 84.2% with a route object
8IPv6 routes 87.5% RPKI valid · 62.5% with a route object
3RPKI invalid 3 origin · 0 maxLength
0No ROA 6 with no route object for this origin
3Low visibility seen by under 10% of full-table peers
10Route objects not announced registered with origin AS1405, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS1405, 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.

66.235.109.0/24 Invalid: origin None 4 1%low visibility 3
66.235.108.0/23 Invalid: origin Other origin only 2 0%low visibility 2
2401:e60:100::/40 Invalid: origin Other origin only 1 0%low visibility 1
169.128.214.0/24 Valid Nonecovered by 169.128.212.0/22 672 100% 66
2a01:4244:2000::/40 Valid Nonecovered by 2a01:4244:2000::/36 636 100% 67
2a01:4244:4000::/40 Valid Nonecovered by 2a01:4244:4000::/36 633 100% 67
154.83.89.0/24 Valid Other IRR onlyRADB 671 100% 67
152.175.175.0/24 Valid Other IRR onlyRADB 670 100% 67
154.83.88.0/24 Valid Other IRR onlyRADB 667 99% 67
2a01:4247:f100::/40 Valid Other IRR onlyRADB 635 100% 70
103.102.5.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.102.6.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
103.102.7.0/24 Valid RIR databaseAPNIC, RADB 671 100% 66
169.128.212.0/22 Valid RIR databaseARIN, RADB 671 100% 67
187.54.56.0/23 Valid RIR databaseAPNIC, RADB 671 100% 66
23.144.76.0/24 Valid RIR databaseARIN, RADB 670 100% 67
103.102.4.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
187.54.56.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
187.54.57.0/24 Valid RIR databaseAPNIC 669 99% 67
216.236.27.0/24 Valid RIR databaseRADB, RIPE 669 99% 67
82.39.160.0/24 Valid RIR databaseRADB, RIPE 668 99% 67
161.129.39.0/24 Valid RIR databaseARIN, RADB 668 99% 67
169.128.55.0/24 Valid RIR databaseARIN, RADB 668 99% 67
2a01:4244:1000::/40 Valid RIR databaseRADB, RIPE 636 100% 67
2a01:4244:2000::/36 Valid RIR databaseRADB, RIPE 636 100% 67
2602:f594::/40 Valid RIR databaseARIN, RADB 633 100% 68
2a01:4244:4000::/36 Valid RIR databaseRIPE 631 99% 67

AS-SET

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

  • ROA: origin3
  • Route object: none6
  • Route object: RIR4
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
ROA: origin66.235.109.0/24ROAs covering it name AS32595, not AS1405. If AS1405 should announce it, add a ROA for AS1405.4 of 673
Route object: none66.235.109.0/24No route object for it. Add a route object with origin AS1405 in the RIR database for the space.4 of 673
ROA: origin66.235.108.0/23ROAs covering it name AS32595, not AS1405. If AS1405 should announce it, add a ROA for AS1405.2 of 673
Route object: none66.235.108.0/23Route objects for it name AS32595. Add a route object with origin AS1405 in the RIR database for the space.2 of 673
ROA: origin2401:e60:100::/40ROAs covering it name AS139358, not AS1405. If AS1405 should announce it, add a ROA for AS1405.1 of 636
Route object: none2401:e60:100::/40Route objects for it name AS139358. Add a route object with origin AS1405 in the RIR database for the space.1 of 636
Route object: none169.128.214.0/24No route object for it. A route object for 169.128.212.0/22 with origin AS1405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1405 in the RIR database for the space.672 of 673
Route object: none2a01:4244:2000::/40No route object for it. A route object for 2a01:4244:2000::/36 with origin AS1405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1405 in the RIR database for the space.636 of 636
Route object: none2a01:4244:4000::/40No route object for it. A route object for 2a01:4244:4000::/36 with origin AS1405 covers it (filters allowing more-specifics accept it). Add a route object with origin AS1405 in the RIR database for the space.633 of 636
Route object: RIR154.83.89.0/24Route object only in RADB. Add it in the RIR database for the space.671 of 673
Route object: RIR152.175.175.0/24Route object only in RADB. Add it in the RIR database for the space.670 of 673
Route object: RIR154.83.88.0/24Route object only in RADB. Add it in the RIR database for the space.667 of 673
Route object: RIR2a01:4247:f100::/40Route object only in RADB. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

12.156.222.0/24RADBNo ROA
45.192.242.0/23AFRINICInvalid: origin
103.102.4.0/22APNICValid
103.102.4.0/23APNICValid
103.102.6.0/23APNICValid
154.83.88.0/23AFRINIC, RADBValid
216.195.216.0/22RIPEValid
2a01:4244::/30RADBValid
2a01:4247:f000::/40RIPEValid
2a13:9500:1a2::/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.