bgpreport

Network · data from 2026-11-12

AS22843 PROOFPOINT-ASN-US-EAST - Proofpoint, Inc.

Registry name: PROOFPOINT-ASN-US-EAST - Proofpoint, Inc., US · not in PeeringDB

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

Announced routes

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

208.83.137.0/24 No ROA RIR databaseARIN 673 100% 67
208.83.139.0/24 No ROA RIR databaseARIN 673 100% 67
2620:0:2902::/48 No ROA RIR databaseARIN 635 100% 67
2620:0:2900::/48 No ROA RIR databaseARIN 554 87% 62
66.159.250.0/23 Valid Nonecovered by 66.159.224.0/19 673 100% 67
148.163.152.0/22 Valid None 673 100% 67
148.163.158.0/23 Valid None 673 100% 67
66.159.228.0/24 Valid RIR databaseARIN 673 100% 67
66.159.238.0/23 Valid RIR databaseARIN 673 100% 67
66.159.250.0/24 Valid RIR databaseARIN 673 100% 67
66.159.251.0/24 Valid RIR databaseARIN 673 100% 67
67.231.152.0/24 Valid RIR databaseARIN 673 100% 67
67.231.153.0/24 Valid RIR databaseARIN 673 100% 67
67.231.154.0/24 Valid RIR databaseARIN 673 100% 67
67.231.155.0/24 Valid RIR databaseARIN 673 100% 67
67.231.156.0/24 Valid RIR databaseARIN 673 100% 67
67.231.157.0/24 Valid RIR databaseARIN 673 100% 67
148.163.136.0/24 Valid RIR databaseARIN 673 100% 67
148.163.137.0/24 Valid RIR databaseARIN 673 100% 67
148.163.138.0/24 Valid RIR databaseARIN 673 100% 67
148.163.139.0/24 Valid RIR databaseARIN 673 100% 67
148.163.140.0/24 Valid RIR databaseARIN 673 100% 67
148.163.141.0/24 Valid RIR databaseARIN 673 100% 67
148.163.142.0/24 Valid RIR databaseARIN 673 100% 67
148.163.143.0/24 Valid RIR databaseARIN 673 100% 67
205.220.172.0/24 Valid RIR databaseARIN 673 100% 67
205.220.173.0/24 Valid RIR databaseARIN 673 100% 67
205.220.174.0/24 Valid RIR databaseARIN 673 100% 67
205.220.175.0/24 Valid RIR databaseARIN 673 100% 67
205.220.176.0/24 Valid RIR databaseARIN 673 100% 67
205.220.177.0/24 Valid RIR databaseARIN 673 100% 67
205.220.178.0/24 Valid RIR databaseARIN 673 100% 67
205.220.179.0/24 Valid RIR databaseARIN 673 100% 67
205.220.180.0/24 Valid RIR databaseARIN 673 100% 67
205.220.181.0/24 Valid RIR databaseARIN 673 100% 67
205.220.182.0/24 Valid RIR databaseARIN 673 100% 67
205.220.183.0/24 Valid RIR databaseARIN 673 100% 67
205.220.187.0/24 Valid RIR databaseARIN 673 100% 67
208.56.12.0/24 Valid RIR databaseARIN 673 100% 67
208.56.13.0/24 Valid RIR databaseARIN 673 100% 67
208.56.14.0/24 Valid RIR databaseARIN 673 100% 67
208.56.15.0/24 Valid RIR databaseARIN 673 100% 67
208.56.60.0/24 Valid RIR databaseARIN 673 100% 67
208.56.61.0/24 Valid RIR databaseARIN 673 100% 67
208.56.62.0/24 Valid RIR databaseARIN 673 100% 67
208.56.63.0/24 Valid RIR databaseARIN 673 100% 67
208.84.67.0/24 Valid RIR databaseARIN 673 100% 67
208.86.201.0/24 Valid RIR databaseARIN 673 100% 67
2620:100:9004::/47 Valid RIR databaseARIN 635 100% 67

AS-SET

AS22843 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 15 are in fix.csv.

  • ROA: none4
  • Route object: none3
  • Route object: not announced8
ChangePrefix or setDetailFull-table peers
ROA: none208.83.137.0/24No ROA covers it. Add a ROA for AS22843, maxLength 24.673 of 673
ROA: none208.83.139.0/24No ROA covers it. Add a ROA for AS22843, maxLength 24.673 of 673
ROA: none2620:0:2902::/48No ROA covers it. Add a ROA for AS22843, maxLength 48.635 of 636
ROA: none2620:0:2900::/48No ROA covers it. Add a ROA for AS22843, maxLength 48.554 of 636
Route object: none66.159.250.0/23No route object for it. A route object for 66.159.224.0/19 with origin AS22843 covers it (filters allowing more-specifics accept it). Add a route object with origin AS22843 in the RIR database for the space.673 of 673
Route object: none148.163.152.0/22No route object for it. Add a route object with origin AS22843 in the RIR database for the space.673 of 673
Route object: none148.163.158.0/23No route object for it. Add a route object with origin AS22843 in the RIR database for the space.673 of 673

Route objects not announced

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

66.159.224.0/19ARINValid
148.163.152.0/24ARINValid
148.163.153.0/24ARINValid
148.163.154.0/24ARINValid
148.163.155.0/24ARINValid
148.163.158.0/24ARINValid
148.163.159.0/24ARINValid
208.56.0.0/18ARINInvalid: origin

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.