bgpreport

Network · data from 2026-11-12

AS5504 LOGOSNET

Registry name: LOGOSNET Logosnet Services Limited, CY · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS5504, 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.
213.169.157.0/24 Valid None 673 100% 67
2a01:6700::/32 Valid None 635 100% 67
82.114.32.0/22 Valid RIR databaseRIPE 673 100% 67
82.114.36.0/22 Valid RIR databaseRIPE 673 100% 67
82.114.40.0/22 Valid RIR databaseRIPE 673 100% 67
82.114.51.0/24 Valid RIR databaseRIPE 673 100% 66
82.114.52.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
82.114.56.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
82.114.60.0/22 Valid RIR databaseRIPE 673 100% 67
194.30.128.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.130.0/24 Valid RIR databaseRIPE 673 100% 67
194.30.131.0/24 Valid RIR databaseRIPE 673 100% 67
194.30.132.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.134.0/24 Valid RIR databaseRIPE 673 100% 67
194.30.135.0/24 Valid RIR databaseRIPE 673 100% 67
194.30.136.0/22 Valid RIR databaseRIPE 673 100% 67
194.30.140.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.143.0/24 Valid RIR databaseRIPE 673 100% 67
194.30.144.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.146.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.148.0/22 Valid RIR databaseRIPE 673 100% 67
194.30.152.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.154.0/23 Valid RIR databaseRIPE 673 100% 67
194.30.156.0/23 Valid RIR databaseRIPE 673 100% 67
213.169.128.0/21 Valid RIR databaseRIPE 673 100% 67
213.169.136.0/22 Valid RIR databaseRIPE 673 100% 67
213.169.140.0/22 Valid RIR databaseRIPE 673 100% 67
213.169.144.0/22 Valid RIR databaseRADB, RIPE 673 100% 67
213.169.158.0/23 Valid RIR databaseRIPE 673 100% 67

AS-SET

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

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none213.169.157.0/24No route object for it. Add a route object with origin AS5504 in the RIR database for the space.673 of 673
Route object: none2a01:6700::/32No route object for it. Add a route object with origin AS5504 in the RIR database for the space.635 of 636

Route objects not announced

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