bgpreport

Network · data from 2026-11-12

AS26380 MasterCard Technologies

Registry name: MASTER-7-AS - MasterCard Technologies LLC, US · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS26380, 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.
156.154.239.0/24 No ROA Other origin only 672 100% 67
12.10.32.0/24 Valid Nonecovered by 12.10.32.0/23 673 100% 70
12.10.33.0/24 Valid Nonecovered by 12.10.32.0/23 673 100% 70
12.22.157.0/24 Valid Nonecovered by 12.22.156.0/23 673 100% 66
12.22.158.0/24 Valid Nonecovered by 12.22.156.0/22 673 100% 67
12.22.159.0/24 Valid Nonecovered by 12.22.156.0/22 673 100% 67
75.141.71.0/24 Valid None 673 100% 67
209.64.210.0/24 Valid Nonecovered by 209.64.210.0/23 673 100% 70
209.64.211.0/24 Valid Nonecovered by 209.64.210.0/23 673 100% 70
12.22.156.0/24 Valid Nonecovered by 12.22.156.0/23 672 100% 67
12.22.152.0/24 Valid Other IRR onlyRADB 673 100% 70
12.22.153.0/24 Valid Other IRR onlyRADB 673 100% 70
12.22.154.0/24 Valid Other IRR onlyRADB 673 100% 70
12.22.155.0/24 Valid Other IRR onlyRADB 673 100% 70
185.175.204.0/23 Valid Other IRR onlyRADB 672 100% 66
12.10.32.0/23 Valid RIR databaseARIN 673 100% 67
12.22.152.0/22 Valid RIR databaseARIN 673 100% 67
45.115.130.0/23 Valid RIR databaseAPNIC 673 100% 67
103.55.150.0/23 Valid RIR databaseAPNIC 673 100% 67
113.30.208.0/24 Valid RIR databaseARIN 673 100% 67
113.30.209.0/24 Valid RIR databaseARIN 673 100% 70
113.30.210.0/24 Valid RIR databaseARIN 673 100% 70
113.30.211.0/24 Valid RIR databaseARIN 673 100% 70
113.30.212.0/24 Valid RIR databaseARIN 673 100% 70
113.30.213.0/24 Valid RIR databaseARIN 673 100% 70
113.30.214.0/24 Valid RIR databaseARIN 673 100% 70
113.30.215.0/24 Valid RIR databaseARIN 673 100% 70
185.96.136.0/23 Valid RIR databaseRIPE 673 100% 67
185.96.137.0/24 Valid RIR databaseRIPE 673 100% 67
185.96.138.0/24 Valid RIR databaseRADB, RIPE 673 100% 67
205.233.71.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.208.0/22 Valid RIR databaseARIN 673 100% 67
216.119.208.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.209.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.210.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.213.0/24 Valid RIR databaseARIN 673 100% 67
216.119.214.0/24 Valid RIR databaseARIN 673 100% 67
216.119.215.0/24 Valid RIR databaseARIN 673 100% 67
216.119.216.0/22 Valid RIR databaseARIN 673 100% 67
216.119.216.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.217.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.218.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.219.0/24 Valid RIR databaseARIN, RADB 673 100% 70
216.119.222.0/24 Valid RIR databaseARIN 673 100% 70
216.119.223.0/24 Valid RIR databaseARIN, RADB 673 100% 70
217.149.105.0/24 Valid RIR databaseRIPE 673 100% 70
217.149.106.0/24 Valid RIR databaseRIPE 673 100% 67
217.149.107.0/24 Valid RIR databaseRIPE 673 100% 67
220.101.52.0/24 Valid RIR databaseAPNIC 673 100% 67
45.115.128.0/23 Valid RIR databaseAPNIC 672 100% 67
103.55.148.0/23 Valid RIR databaseAPNIC 672 100% 67
103.55.148.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.55.149.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.55.150.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
103.55.151.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
180.92.176.0/24 Valid RIR databaseAPNIC, RADB 672 100% 67
185.96.136.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.175.204.0/24 Valid RIR databaseRIPE 672 100% 67
185.175.205.0/24 Valid RIR databaseRIPE 672 100% 67
185.175.206.0/23 Valid RIR databaseNTTCOM, RADB, RIPE 672 100% 67
185.175.207.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.199.60.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
185.199.61.0/24 Valid RIR databaseRADB, RIPE 672 100% 67
45.115.128.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.115.129.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
45.115.130.0/24 Valid RIR databaseAPNIC, RADB 671 100% 67
185.175.206.0/24 Valid RIR databaseRADB, RIPE 671 100% 67
14.102.177.0/24 Valid RIR databaseAPNIC, RADB 669 99% 67
2607:3c00:6404::/47 Valid RIR databaseARIN, RADB 636 100% 67
2607:3c00:6404::/48 Valid RIR databaseARIN, RADB 636 100% 67
2607:3c00:6414::/48 Valid RIR databaseARIN, RADB 636 100% 67
2607:3c00:6414::/47 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS26380'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 40 are in fix.csv.

  • ROA: none1
  • Route object: none10
  • Route object: RIR5
  • Route object: not announced24
ChangePrefix or setDetailFull-table peers
ROA: none156.154.239.0/24No ROA covers it. Add a ROA for AS26380, maxLength 24.672 of 673
Route object: none156.154.239.0/24Route objects for it name AS19905. Add a route object with origin AS26380 in the RIR database for the space.672 of 673
Route object: none12.10.32.0/24No route object for it. A route object for 12.10.32.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none12.10.33.0/24No route object for it. A route object for 12.10.32.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none12.22.157.0/24No route object for it. A route object for 12.22.156.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none12.22.158.0/24No route object for it. A route object for 12.22.156.0/22 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none12.22.159.0/24No route object for it. A route object for 12.22.156.0/22 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none75.141.71.0/24No route object for it. Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none209.64.210.0/24No route object for it. A route object for 209.64.210.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none209.64.211.0/24No route object for it. A route object for 209.64.210.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.673 of 673
Route object: none12.22.156.0/24No route object for it. A route object for 12.22.156.0/23 with origin AS26380 covers it (filters allowing more-specifics accept it). Add a route object with origin AS26380 in the RIR database for the space.672 of 673
Route object: RIR12.22.152.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR12.22.153.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR12.22.154.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR12.22.155.0/24Route object only in RADB. Add it in the RIR database for the space.673 of 673
Route object: RIR185.175.204.0/23Route object only in RADB. Add it in the RIR database for the space.672 of 673

Route objects not announced

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

12.22.156.0/22ARINValid
12.22.156.0/23RADBValid
14.102.176.0/22RADBNo ROA
14.102.179.0/24RADBNo ROA
45.115.131.0/24APNIC, RADBValid
64.95.146.0/23RADBNo ROA
64.95.146.0/24RADBNo ROA
64.95.147.0/24RADBNo ROA
66.150.213.0/24RADBNo ROA
92.43.40.0/24RIPEValid
92.43.41.0/24RIPEValid
103.55.148.0/22RADBNo ROA
180.92.176.0/23APNIC, RADBValid
180.92.177.0/24APNICValid
185.96.138.0/23RIPENo ROA
185.96.139.0/24RIPENo ROA
185.175.204.0/22RADBNo ROA
185.199.62.0/24RIPENo ROA
209.64.210.0/23ARIN, RADBValid
216.119.211.0/24ARINInvalid: maxLength
2607:3c00:6401::/48ARIN, RADBNo ROA
2607:3c00:6411::/48RADBNo ROA
2607:3c00:6801::/48ARIN, RADBNo ROA
2607:3c00:6811::/48ARIN, RADBNo 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.