bgpreport

Network · data from 2026-11-12

AS132513 SKYTELLAO-AS-AP - Sky Telecom State Company

Registry name: SKYTELLAO-AS-AP - Sky Telecom State Company, LA · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS132513, 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.
154.84.180.0/24 Invalid: origin Other origin only 2 0%low visibility 1
154.85.98.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 671 100% 67
154.91.139.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 671 100% 67
154.197.44.0/24 Valid RIR databaseAFRINIC, RADB 671 100% 67
156.226.4.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 671 100% 67
154.215.15.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 668 99% 67
45.195.145.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 667 99% 67
45.204.66.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 667 99% 67
45.204.67.0/24 Valid RIR databaseAFRINIC, NTTCOM, RADB 667 99% 67

AS-SET

AS132513 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 18 are in fix.csv.

  • ROA: origin1
  • Route object: none1
  • Route object: not announced16
ChangePrefix or setDetailFull-table peers
ROA: origin154.84.180.0/24ROAs covering it name AS17561, not AS132513. If AS132513 should announce it, add a ROA for AS132513.2 of 673
Route object: none154.84.180.0/24Route objects for it name AS17561, AS401362. Add a route object with origin AS132513 in the RIR database for the space.2 of 673

Route objects not announced

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

45.196.208.0/24AFRINICInvalid: origin
45.200.151.0/24AFRINICInvalid: origin
45.204.66.0/23RADBNo ROA
45.207.164.0/24AFRINICInvalid: origin
45.207.165.0/24AFRINICInvalid: origin
45.207.166.0/24AFRINICInvalid: origin
45.207.167.0/24AFRINICInvalid: origin
103.107.11.0/24NTTCOMNo ROA
103.140.246.0/23NTTCOMNo ROA
103.140.246.0/24RADBNo ROA
103.140.247.0/24NTTCOM, RADBNo ROA
103.238.164.0/24NTTCOM, RADBNo ROA
154.92.12.0/23NTTCOM, RADBNo ROA
154.197.8.0/22NTTCOMNo ROA
154.208.132.0/22RADBNo ROA
154.222.37.0/24AFRINIC, RADBValid

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.