bgpreport

Network · data from 2026-11-12

AS40444 Constant Contact, Inc.

Registry name: ASN-CC - Constant Contact, Inc, US · PeeringDB

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

Announced routes

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

205.207.104.0/23 No ROA Other origin onlycovered by 205.207.104.0/22 673 100% 67
208.75.120.0/23 No ROA Other origin onlycovered by 208.75.120.0/22 673 100% 67
216.21.230.0/24 No ROA Other origin only 673 100% 67
205.207.104.0/24 No ROA Other origin onlycovered by 205.207.104.0/22 672 100% 67
205.207.106.0/23 No ROA Other origin onlycovered by 205.207.104.0/22 671 100% 67
208.75.122.0/23 No ROA Other origin onlycovered by 208.75.120.0/22 671 100% 67

AS-SET

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

  • ROA: none6
  • Route object: none6
  • Route object: not announced6
ChangePrefix or setDetailFull-table peers
ROA: none205.207.104.0/23No ROA covers it. Add a ROA for AS40444, maxLength 23.673 of 673
Route object: none205.207.104.0/23Route objects for it name AS46887. A route object for 205.207.104.0/22 with origin AS40444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40444 in the RIR database for the space.673 of 673
ROA: none208.75.120.0/23No ROA covers it. Add a ROA for AS40444, maxLength 23.673 of 673
Route object: none208.75.120.0/23Route objects for it name AS19871, AS46606, AS137443, AS393842. A route object for 208.75.120.0/22 with origin AS40444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40444 in the RIR database for the space.673 of 673
ROA: none216.21.230.0/24No ROA covers it. Add a ROA for AS40444, maxLength 24.673 of 673
Route object: none216.21.230.0/24Route objects for it name AS398427. Add a route object with origin AS40444 in the RIR database for the space.673 of 673
ROA: none205.207.104.0/24No ROA covers it. Add a ROA for AS40444, maxLength 24.672 of 673
Route object: none205.207.104.0/24Route objects for it name AS398427. A route object for 205.207.104.0/22 with origin AS40444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40444 in the RIR database for the space.672 of 673
ROA: none205.207.106.0/23No ROA covers it. Add a ROA for AS40444, maxLength 23.671 of 673
Route object: none205.207.106.0/23Route objects for it name AS46887. A route object for 205.207.104.0/22 with origin AS40444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40444 in the RIR database for the space.671 of 673
ROA: none208.75.122.0/23No ROA covers it. Add a ROA for AS40444, maxLength 23.671 of 673
Route object: none208.75.122.0/23Route objects for it name AS46887. A route object for 208.75.120.0/22 with origin AS40444 covers it (filters allowing more-specifics accept it). Add a route object with origin AS40444 in the RIR database for the space.671 of 673

Route objects not announced

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

205.207.104.0/22ALTDB, RADBNo ROA
205.207.106.0/24RADBNo ROA
205.207.107.0/24RADBNo ROA
208.75.120.0/22ALTDB, RADBNo ROA
208.75.122.0/24RADBNo ROA
208.75.123.0/24RADBNo 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.