bgpreport

Network · data from 2026-11-12

AS64411 CORREOS-TELECOM

Registry name: CORREOS-TELECOM Correos Telecom SA S.M.E., ES · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS64411, 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.
158.172.96.0/24 Invalid: origin Other origin onlycovered by 158.172.0.0/17 82 12% 39
158.172.0.0/21 Valid RIR databaseRIPE 673 100% 67
185.165.164.0/22 Valid RIR databaseRIPE 673 100% 67
2a0a:3e00::/29 Valid RIR databaseRIPE 634 100% 67

AS-SET

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

  • ROA: origin1
  • Route object: none1
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin158.172.96.0/24ROAs covering it name AS61388, not AS64411. If AS64411 should announce it, add a ROA for AS64411.82 of 673
Route object: none158.172.96.0/24Route objects for it name AS61388. A route object for 158.172.0.0/17 with origin AS64411 covers it (filters allowing more-specifics accept it). Add a route object with origin AS64411 in the RIR database for the space.82 of 673

Route objects not announced

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

158.172.0.0/17RIPENo ROA

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.