bgpreport

Network · data from 2026-11-12

AS31128 SHAZAM-AS Apple Distribution International Ltd.

Registry name: SHAZAM-AS Apple Distribution International Ltd., IE · not in PeeringDB

11IPv4 routes 9.1% RPKI valid · 36.4% with a route object
18IPv6 routes 11.1% RPKI valid · 27.8% with a route object
12RPKI invalid 12 origin · 0 maxLength
14No ROA 20 with no route object for this origin
13Low visibility seen by under 10% of full-table peers
3Route objects not announced registered with origin AS31128, seen from no peer

Announced routes

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

2605:5e00:1101::/56 Invalid: origin None 7 1%low visibility 7
2c0f:fd58:0:600::/56 Invalid: origin None 2 0%low visibility 1
178.210.56.64/27 Invalid: origin None 1 0%low visibility 1
187.251.64.32/27 Invalid: origin None 1 0%low visibility 1
216.17.29.128/27 Invalid: origin None 1 0%low visibility 1
2001:d98:c00:100::/56 Invalid: origin None 1 0%low visibility 1
2001:43e8:0:1100::/56 Invalid: origin None 1 0%low visibility 1
2605:8400:20b::/56 Invalid: origin None 1 0%low visibility 1
2804:3674:0:2500::/56 Invalid: origin None 1 0%low visibility 1
2806:202:6:200::/56 Invalid: origin None 1 0%low visibility 1
2a00:1440:0:100::/56 Invalid: origin None 1 0%low visibility 1
2c0f:ffd8:0:1100::/56 Invalid: origin None 1 0%low visibility 1
139.178.192.0/24 No ROA Nonecovered by 139.178.192.0/18 673 100% 67
139.178.193.0/24 No ROA Nonecovered by 139.178.192.0/18 673 100% 67
139.178.194.0/24 No ROA Nonecovered by 139.178.192.0/18 673 100% 67
139.178.195.0/24 No ROA Nonecovered by 139.178.192.0/18 673 100% 67
2a01:b746:100::/48 No ROA None 604 95% 68
2a01:b746:101::/48 No ROA None 604 95% 68
2a01:b746:102::/48 No ROA None 604 95% 68
2a01:b746:103::/48 No ROA None 604 95% 68
139.178.196.0/24 No ROA Other IRR onlyRADB 673 100% 67
139.178.197.0/24 No ROA Other IRR onlyRADB 673 100% 67
139.178.198.0/24 No ROA Other IRR onlyRADB 673 100% 67
2a01:b746:104::/48 No ROA Other IRR onlyRADB 636 100% 69
2a01:b746:105::/48 No ROA Other IRR onlyRADB 636 100% 69
2a01:b746:106::/48 No ROA Other IRR onlyRADB 636 100% 69
2a0f:3400:500::/48 Valid RIR databaseRIPE 635 100% 67
2803:3b80:c020::/48 Valid RIR databaseLACNIC 321 50% 64
88.209.219.0/27 Valid RIR databaseRIPE 34 5%low visibility 25

AS-SET

AS31128 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 55 are in fix.csv.

  • ROA: origin12
  • ROA: none14
  • Route object: none20
  • Route object: RIR6
  • Route object: not announced3
ChangePrefix or setDetailFull-table peers
ROA: origin2605:5e00:1101::/56ROAs covering it name AS40317, not AS31128. If AS31128 should announce it, add a ROA for AS31128.7 of 636
Route object: none2605:5e00:1101::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.7 of 636
ROA: origin2c0f:fd58:0:600::/56ROAs covering it name AS11845, not AS31128. If AS31128 should announce it, add a ROA for AS31128.2 of 636
Route object: none2c0f:fd58:0:600::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.2 of 636
ROA: origin178.210.56.64/27ROAs covering it name AS43727, AS44604, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 673
Route object: none178.210.56.64/27No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 673
ROA: origin187.251.64.32/27ROAs covering it name AS28458, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 673
Route object: none187.251.64.32/27No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 673
ROA: origin216.17.29.128/27ROAs covering it name AS10242, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 673
Route object: none216.17.29.128/27No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 673
ROA: origin2001:d98:c00:100::/56ROAs covering it name AS18106, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2001:d98:c00:100::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2001:43e8:0:1100::/56ROAs covering it name AS37105, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2001:43e8:0:1100::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2605:8400:20b::/56ROAs covering it name AS10242, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2605:8400:20b::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2804:3674:0:2500::/56ROAs covering it name AS37468, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2804:3674:0:2500::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2806:202:6:200::/56ROAs covering it name AS28458, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2806:202:6:200::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2a00:1440:0:100::/56ROAs covering it name AS43727, AS44604, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2a00:1440:0:100::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: origin2c0f:ffd8:0:1100::/56ROAs covering it name AS37105, not AS31128. If AS31128 should announce it, add a ROA for AS31128.1 of 636
Route object: none2c0f:ffd8:0:1100::/56No route object for it. Add a route object with origin AS31128 in the RIR database for the space.1 of 636
ROA: none139.178.192.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: none139.178.192.0/24No route object for it. A route object for 139.178.192.0/18 with origin AS31128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31128 in the RIR database for the space.673 of 673
ROA: none139.178.193.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: none139.178.193.0/24No route object for it. A route object for 139.178.192.0/18 with origin AS31128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31128 in the RIR database for the space.673 of 673
ROA: none139.178.194.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: none139.178.194.0/24No route object for it. A route object for 139.178.192.0/18 with origin AS31128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31128 in the RIR database for the space.673 of 673
ROA: none139.178.195.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: none139.178.195.0/24No route object for it. A route object for 139.178.192.0/18 with origin AS31128 covers it (filters allowing more-specifics accept it). Add a route object with origin AS31128 in the RIR database for the space.673 of 673
ROA: none2a01:b746:100::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.604 of 636
Route object: none2a01:b746:100::/48No route object for it. Add a route object with origin AS31128 in the RIR database for the space.604 of 636
ROA: none2a01:b746:101::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.604 of 636
Route object: none2a01:b746:101::/48No route object for it. Add a route object with origin AS31128 in the RIR database for the space.604 of 636
ROA: none2a01:b746:102::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.604 of 636
Route object: none2a01:b746:102::/48No route object for it. Add a route object with origin AS31128 in the RIR database for the space.604 of 636
ROA: none2a01:b746:103::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.604 of 636
Route object: none2a01:b746:103::/48No route object for it. Add a route object with origin AS31128 in the RIR database for the space.604 of 636
ROA: none139.178.196.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: RIR139.178.196.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none139.178.197.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: RIR139.178.197.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none139.178.198.0/24No ROA covers it. Add a ROA for AS31128, maxLength 24.673 of 673
Route object: RIR139.178.198.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
ROA: none2a01:b746:104::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.636 of 636
Route object: RIR2a01:b746:104::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a01:b746:105::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.636 of 636
Route object: RIR2a01:b746:105::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636
ROA: none2a01:b746:106::/48No ROA covers it. Add a ROA for AS31128, maxLength 48.636 of 636
Route object: RIR2a01:b746:106::/48Route object only in RADB. Add it in the RIR database for the space.636 of 636

Route objects not announced

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

103.142.152.128/27APNICValid
139.178.192.0/18RADBNo ROA
2a01:b746:200::/40RADBNo 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.