bgpreport

Network · data from 2026-11-12

AS13916 PROOFPOINT-UT7 - Proofpoint, Inc.

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

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS13916, 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.136.0/24 No ROA RIR databaseARIN 673 100% 67
208.83.138.0/24 No ROA RIR databaseARIN, RADB 673 100% 67
2620:0:2901::/48 No ROA RIR databaseARIN 635 100% 67
2620:0:2900::/48 No ROA RIR databaseARIN 81 13% 23
148.163.128.0/24 Valid RIR databaseARIN 673 100% 67
148.163.129.0/24 Valid RIR databaseARIN 673 100% 67
148.163.130.0/24 Valid RIR databaseARIN 673 100% 67
2620:100:9008::/47 Valid RIR databaseARIN, RADB 635 100% 67

AS-SET

AS13916 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 16 are in fix.csv.

  • ROA: none4
  • Route object: not announced12
ChangePrefix or setDetailFull-table peers
ROA: none208.83.136.0/24No ROA covers it. Add a ROA for AS13916, maxLength 24.673 of 673
ROA: none208.83.138.0/24No ROA covers it. Add a ROA for AS13916, maxLength 24.673 of 673
ROA: none2620:0:2901::/48No ROA covers it. Add a ROA for AS13916, maxLength 48.635 of 636
ROA: none2620:0:2900::/48No ROA covers it. Add a ROA for AS13916, maxLength 48.81 of 636

Route objects not announced

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

66.159.224.0/19RADBValid
66.159.224.0/24ARINValid
66.159.229.0/24ARINValid
148.163.131.0/24ARINValid
148.163.132.0/24ARINValid
148.163.133.0/24ARINValid
148.163.134.0/24ARINValid
148.163.135.0/24ARINValid
205.220.160.0/19RADBValid
208.56.0.0/18ARINValid
208.83.136.0/22RADBNo ROA
2620:0:2900::/44RADBNo 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.