bgpreport

Network · data from 2026-11-12

AS205080 SITA-CORPORATE Societe Internationale de Telecommunications Aeronautiques

Registry name: SITA-CORPORATE Societe Internationale de Telecommunications Aeronautiques, BE · not in PeeringDB

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

Announced routes

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

2a02:9010:d4::/48 Invalid: origin None 2 0%low visibility 2
2a0a:90c0:1000::/42 Valid None 635 100% 68
57.188.4.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.8.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.15.0/24 Valid RIR databaseRIPE 673 100% 66
57.188.18.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.19.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.23.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.26.0/24 Valid RIR databaseRIPE 673 100% 66
57.188.27.0/24 Valid RIR databaseRIPE 673 100% 67
57.188.32.0/22 Valid RIR databaseRIPE 673 100% 67
57.188.38.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
57.188.49.0/24 Valid RIR databaseRIPE 673 100% 66
57.188.63.0/24 Valid RIR databaseRIPE 673 100% 66
57.188.20.0/24 Valid RIR databaseRIPE 672 100% 67
57.188.22.0/24 Valid RIR databaseRIPE 672 100% 66
57.188.37.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
57.188.40.0/24 Valid RIR databaseRIPE 672 100% 67
57.188.41.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
57.188.42.0/24 Valid RIR databaseRADB, RIPE 672 100% 66
57.188.52.0/24 Valid RIR databaseRIPE 672 100% 66
57.188.7.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.9.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.10.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.11.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.14.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.24.0/24 Valid RIR databaseRIPE 671 100% 67
57.188.25.0/24 Valid RIR databaseRIPE 671 100% 68
57.188.28.0/22 Valid RIR databaseRIPE 671 100% 68
57.188.51.0/24 Valid RIR databaseRIPE 671 100% 66
57.188.55.0/24 Valid RIR databaseRIPE 671 100% 66
57.188.56.0/24 Valid RIR databaseRIPE 671 100% 66
57.188.16.0/24 Valid RIR databaseRIPE 670 100% 67
57.188.17.0/24 Valid RIR databaseRIPE 670 100% 67
57.188.61.0/24 Valid RIR databaseRIPE 669 99% 67
2a0a:90c0:1043::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:90c0:1070::/48 Valid RIR databaseRIPE 636 100% 69
2a0a:90c0:1085::/48 Valid RIR databaseRIPE 636 100% 70
2a0a:90c0:1090::/48 Valid RIR databaseRIPE 636 100% 67
2a0a:90c0:1010::/48 Valid RIR databaseRADB, RIPE 635 100% 69
2a0a:90c0:1047::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:90c0:1049::/48 Valid RIR databaseRIPE 635 100% 70
2a0a:90c0:104c::/48 Valid RIR databaseRIPE 635 100% 67
2a0a:90c0:105c::/48 Valid RIR databaseRIPE 635 100% 68
2a0a:90c0:1084::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:90c0:10c1::/48 Valid RIR databaseRIPE 635 100% 69
2a0a:90c0:1058::/48 Valid RIR databaseRIPE 634 100% 68
2a0a:90c0:1062::/48 Valid RIR databaseRIPE 634 100% 68
2a0a:90c0:1003::/48 Valid RIR databaseRIPE 633 100% 69
2a0a:90c0:1052::/48 Valid RIR databaseRIPE 629 99% 67

AS-SET

AS205080 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 30 are in fix.csv.

  • ROA: origin1
  • Route object: none2
  • Route object: not announced27
ChangePrefix or setDetailFull-table peers
ROA: origin2a02:9010:d4::/48ROAs covering it name AS3352, not AS205080. If AS205080 should announce it, add a ROA for AS205080.2 of 636
Route object: none2a02:9010:d4::/48No route object for it. Add a route object with origin AS205080 in the RIR database for the space.2 of 636
Route object: none2a0a:90c0:1000::/42No route object for it. Add a route object with origin AS205080 in the RIR database for the space.635 of 636

Route objects not announced

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

57.188.0.0/22RIPEValid
57.188.5.0/24RIPEValid
57.188.6.0/24RIPEValid
57.188.36.0/24RIPEValid
57.188.43.0/24RIPEValid
57.188.59.0/24RADBValid
2a0a:90c0:1000::/48RIPEValid
2a0a:90c0:1002::/48RIPEValid
2a0a:90c0:1004::/48RADB, RIPEValid
2a0a:90c0:101c::/48RADB, RIPEValid
2a0a:90c0:101d::/48RADB, RIPEValid
2a0a:90c0:1055::/48RIPEValid
2a0a:90c0:105d::/48RIPEValid
2a0a:90c0:105f::/48RIPEValid
2a0a:90c0:1066::/48RIPEValid
2a0a:90c0:1069::/48RIPEValid
2a0a:90c0:106a::/48RIPEValid
2a0a:90c0:1081::/48RIPEValid
2a0a:90c0:1083::/48RIPEValid
2a0a:90c0:1088::/48RIPEValid
2a0a:90c0:108a::/48RIPEValid
2a0a:90c0:108c::/48RIPEValid
2a0a:90c0:1092::/48RIPEValid
2a0a:90c0:1096::/48RIPEValid
2a0a:90c0:10c0::/48RIPEValid
2a0a:90c0:10d0::/48RIPEValid
2a0a:90c0:10d2::/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.