Cloud Management Console Release

Maintenance window: September 04, 2017 04:01 UTC to September 04, 2017 08:00 UTC Impacted Cloud services:

• Cloud Management Console

  • Add support for dynamic header values in SAP identity provider

Impact Level : minor

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Identity Services Release

Maintenance window: September 04, 2017 00:01 UTC to September 04, 2017 04:00 UTC Impacted Cloud services:

• Identity Services

  • Add support for dynamic header values in SAP identity provider

Impact Level : minor

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Management Services Release

Maintenance window: August 28, 2017 00:01 to August 28, 2017 04:00 Impacted Cloud services:

• Management Services

  • Fix MobileFabric Identity login issue if user does not have email id

  • Update MDM signing certificate which is going to be expired soon

  • Fix Loop of Expiry Notification issue for all certificates

Impact Level : minor

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Reporting Services - delayed processing

Incident window: August 22, 2017 07:40 UTC to February 22, 2018 03:00 UTC Impacted Cloud services:

• Cloud Reports and analytics

  • Delayed processing of reporting / analytics messages

Impact Level : medium

[August 22 07:40 UTC] We have detected performance issues in the processing of messages related to reports / analytics.

[August 22 14:59 UTC] We are continuing to investigate the issue and address.

[August 27 16:22 UTC] We are continuing our recovery efforts. Customer data has been loaded up to 02:30 UTC August 24.

[September 5 13:30 UTC] Delayed analytics have been processed for all services except for Kony Integration Server, which we are continuing to work on. We will continue to provide updates as early as possible.

[September 5 19:59 UTC] The root cause has been identified and we are working to process the message backlog. Currently, ALL data has been processed into the system except Kony Server analytics, which is a backlog of approximately 60 million messages. We are working very hard to ensure no data is lost as we process this backlog. We are expecting that the existing backlog will be in place by EOD Thursday, but systems are continuing to report analytics. We expect to make another update tomorrow to report processing progress.

[September 6 11:37 UTC] We are continuing to process the backlog of Kony Server analytics messages, which is approximately 45 million messages. We are working very hard to ensure no data is lost as we process this backlog. We are expecting that the existing backlog will be in place by EOD Thursday. Analytics for all other Kony services continue to be processed normally.

[September 6 23:04 UTC] We are continuing to steadily process the backlog of Kony Server analytics messages and still anticipating its completion by EOD Thursday.

[September 7 12:20 UTC] We are continuing to steadily process the backlog of Kony Server analytics messages and still anticipating its completion by EOD Thursday.

[September 7 20:01 UTC] We are continuing to steadily process the backlog of Kony Server analytics messages. We are anticipating completion as early as EOD Thursday, but more likely by EOD Friday.

[September 8 12:04 UTC] We are continuing to steadily process the backlog of Kony Server analytics messages. After further review, we anticipate completion by EOD Tuesday.

[September 9 00:17 UTC] We are continuing to steadily process the backlog of Kony Server analytics messages. We are anticipating completion by EOD Tuesday.

[September 20 12:38 UTC] We apologize for additional delays. We have reconsidered our original approach and have adjusted our solution. We are expecting to finish loading the backlog of Kony Server analytics messages by September 23 EOD.

[September 20 23:22 UTC] Kony has scaled up the data warehouse subsystem by 9x, and is making better progress on ingesting our backlog. Customers should already see a marked improvement in most of the Kony analytics reports. Currently, along with the predicted inbound data, we are expecting to be able to deplete the backload in approximately 100 hours (approximately September 24 EOD).

[September 21 11:22 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating completion by September 24 EOD.

[September 22 01:28 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating completion by September 24 EOD.

[September 22 11:32 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating completion by September 24 EOD.

[September 22 20:49 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating completion by September 24 EOD.

[September 25 14:01 UTC] We are continuing to process the backlog of messages. The processing of messages is not ordered by date so gaps may be noticed in reports until a larger batch of messages has been processed. We anticipate that messages up through September 25 04:30 UTC will be processed by October 2 EOD.

[September 26 13:37 UTC] We are continuing to process the backlog of messages. We are checkpointing the load process to process all analytics data up through September 25 04:30 UTC to provide better estimates. We anticipate that those messages will be processed by October 1 EOD.

[September 26 20:12 UTC] We are continuing to process the backlog of messages. We are still anticipating that analytics data up through September 25 04:30 UTC will be processed by October 1 EOD.

[September 27 14:54 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating that analytics data up through September 25 04:30 UTC will be processed by October 1 EOD.

[September 28 00:05 UTC] We are continuing to steadily process the backlog of messages. We are still anticipating that analytics data up through September 25 04:30 UTC will be processed by October 1 EOD.

[September 28 14:14 UTC] As of 13:30 UTC, we have approximately 50,000 files to load to finish ingesting all analytics data up to September 25 04:30 UTC. We are processing files at a velocity of 1500 files / hour, which yields about 34 hours remaining. Our estimate to complete improves slightly and we now anticipate processing to be completed by September 30 EOD.

[September 28 23:01 UTC] We have approximately 33,000 files to load to finish ingesting all analytics data up to September 25 04:30 UTC. We are processing files at a velocity of approximately 1800 files / hour, which translates to about 19 hours remaining. Our estimate to complete improves slightly and we now anticipate processing to be completed by September 29 EOD.

[September 29 13:20 UTC] As of 12:30 UTC we have to load 16,718 files to get all analytics data ingested up to September 25 04:30 UTC. These are some of the larger files and processing has slowed to just under 700 files / hour now, giving an estimate of about 24 hours to finish.

[September 29 21:53 UTC] As of 21:00 UTC, we have to load 9,913 files to ingest the analytics data up to September 25 04:30 UTC. These are some of the larger files, but processing has increased to 1150 files / hour now giving an estimate of about 8.5 hours to finish.

[September 30 15:29 UTC] As of 15:00 UTC, all analytics data up to September 25 04:30 UTC has been processed.

[October 1 17:13 UTC] Database maintenance is in progress; all customer standard and custom reports are available. There my be a minor performance impact during the maintenance. Processing of the analytics data will commence once the database maintenance is concluded.

[October 2 20:10 UTC] Database maintenance has completed. We have pulled in all analytics data up to October 2 20:00 UTC and have begun processing the data. We expect to have all infrastructure analytics processed by 22:00 UTC, with the exception of Kony Server analytics and events. We will provide an estimate for the 75M Kony Server records at 22:00 UTC.

[October 2 21:35 UTC] All infrastructure analytics have been processed up to October 2 20:00 UTC with the exception of Kony Server analytics and events. We will provide an estimate for the 75M Kony Server analytics records at 22:00 UTC.

[October 2 22:15 UTC] We estimate it will take approximately 20 hours to validate, process, and persist the 70M Kony Server analytics records to disk for loading into the data warehouse. Assuming a processing rate of 1400 / hr, it will take approximately 24 hours to load the data. These processes will be executed in parallel. We will have a more precise estimate once all records are persisted as there is some variance in the processing and validation.

[October 3 14:40 UTC] Analytics data between Sept 9/25 04:30 UTC and Oct 2nd 20:00 UTC: We have processed 18M analytics records from the holding queues and written them to disk. In parallel, we have loaded 8,700 files into the data warehouse. We are loading files at a rate of 1400 per hour. Message processing has slowed due to the size of a substantial number of records that are oversized. We will provide an estimate for when the data up to Oct 2nd 20:00 UTC will be available for custom reports once all analytics records are processed and written to disk.

[October 6 11:05 UTC] We have exhausted the space for analytics and are in the process of resizing the cluster. Most queries for customer reports should run, but for queries that create large temporary tables, reports may fail. ETA is 20 hours.

[October 17 17:11 UTC] We completed resizing our analytics cluster since our last update and also had to delete approximately 2.6 billion events that were detected as duplicates. We have collected approximately 150 million Server and Sync messages up to Oct 16 04:00 UTC that will be processed into our data warehouse. We are first processing infrastructure analytics (approximately 30,000 files at a rate of 1,800 files / hour). We anticipate this data to be loaded in about 17 hours. Once this data has been loaded, we will begin loading the Server and Sync data up to Oct 16 04:00 UTC.

[October 18 20:15 UTC] All Kony infrastructure analytics have now been loaded up to Oct 18 18:00 UTC. All Kony Fabric Sync events are currently being processed for events up to Oct 18 18:00 UTC, and we project that processing will complete in less than 24hrs. Kony Fabric Server events have been gathered up to at least Oct 18 18:00 UTC and are being staged for processing.

[October 19 10:26 UTC] All Kony infrastructure analytics have now been loaded up to Oct 19 00:00 UTC. All Kony Fabric Sync events have been loadded up to Oct 19 00:00 UTC. Kony Fabric Server events are estimated to be completed in less than 40 hours for events up to Oct 19 00:00 UTC.

[October 19 21:26 UTC] Kony Fabric Server events are now estimated to be loaded up to Oct 19 00:00 UTC in approximately 64 hours.

[October 20 18:11 UTC] Since beginning to load the Kony Server event data at Oct 19 00:00 UTC, we have processed approximately 60 million event payloads to disk into about 100,000 files. We are loading the resulting files into the analytics data warehouse at a rate between 1,700 and 1,900 files per hour. We continue to process the remaining 125 million payloads to disk in parallel with the load process. We expect that an additional 150,000 to 200,000 files will be created, with an estimated completion time of 90 to 110 hours to load all Server data up to Oct 19 00:00 UTC.

[October 23 11:52 UTC] Since beginning to load the Kony Server event data at Oct 19 00:00 UTC, we have processed approximately 126 million event payloads to disk, into approximately 255,000 files. We are loading the resulting files into the analytics data warehouse at approximately 1,700 files per hour. We continue to process the remaining 59 million payloads to disk in parallel with the load process. Expectations are that we will load an additional 85,000 files, with an estimated ingestion time of 90 hours to load all server data up to Oct 19 00:00 UTC.

[October 26 9:58 UTC] Since beginning to load the Kony Server event data at Oct 19 00:00 UTC, we have processed approximately 180 million event payloads to disk, into approximately 375,000 files. We are loading the resulting files into the analytics data warehouse at approximately 1,500 files per hour. All payloads have been processed to disk. Expectations are that we will load the remaining 70,000 files in approximately 46 hours, at which time all data up to Oct 19 00:00 UTC will be available in our analytics system.

[October 26 20:06 UTC] Processing has slowed. We are loading the resulting files into the analytics data warehouse at approximately 1,000 files per hour. Expectations are that we will load the remaining 63,000 files in approximately 60 hours, at which time all data up to Oct 19 00:00 UTC will be available in our analytics system. We are looking at options to increase ingestion rates.

[October 27 19:27 UTC] Processing has slowed. We are loading the resulting files into the analytics data warehouse at approximately 900 files per hour. Expectations are that we will load the remaining 43,000 files in approximately 50 hours, at which time all data up to Oct 19 00:00 UTC will be available in our analytics system. We are looking at options to increase ingestion rates.

[October 28 15:13 UTC] We are loading the resulting files into the analytics data warehouse at approximately 1000 files per hour. Expectations are that we will load the remaining 10,000 files in approximately 10 hours, at which time all data up to Oct 19 00:00 UTC will be available in our analytics system. We are looking at options to increase ingestion rates.

[October 28 23:02 UTC] We are loading the resulting files into the analytics data warehouse at approximately 1000 files per hour. Expectations are that we will load the remaining 2,000 files in approximately 2.5 hours, at which time all data up to Oct 19 00:00 UTC will be available in our analytics system.

[October 29 01:00 UTC] All analytics data up to Oct 19 00:00 UTC is available in our analytics system.

[October 30 00:00 UTC] All Kony Infrastructure Analytics are on-line and available up to Oct 30 00:00 UTC. All Kony MobileFabric Sync Analytics are on-line and available up to Oct 30 00:00 UTC. Kony MobileFabric Server event payloads gathered up to at least Oct 30 00:00 UTC are being validated and processed to disk for ingestion to our analytics system. Kony will provide an ETA for when we expect these analytics to be available once all 120M event payloads are processed.

[October 31 00:30 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 65 million event payloads to disk, into 75,000 files. In parallel, we are loading the resulting files into the analytics data warehouse at approximately 2000 files per hour. 54% of payloads have been processed to disk. Expectations are that we will process the remaining payloads to disk by Nov 01 00:00 UTC and will be able to estimate the time remaining for ingesting this batch of analytics data at that time.

[October 31 19:42 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 98 million event payloads to disk, into 136,000 files. In parallel, we are loading the resulting files into the analytics data warehouse at approximately 2,000 files per hour. 77% of payloads have been processed to disk and 85,000 files have been ingested. We expect to process the remaining payloads to disk by Nov 1 00:00 UTC and will be able to estimate the time remaining for ingesting this batch of analytics data at that time.

[November 1 12:12 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 120 million event payloads to disk, into 196,000 files. In parallel, we have been loading the resulting files into the analytics data warehouse at approximately 1,900 files per hour. 100% of payloads have been processed to disk, and 113,000 files have been ingested. Initial estimates are that we will process the remaining 83,000 files by Nov 3 00:00 UTC.

[November 2 11:31 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 120 million event payloads to disk, into 204,000 files. In parallel, we have been loading the resulting files into the analytics data warehouse at approximately 2,000 files per hour. 100% of payloads have been processed to disk, and 158,500 files have been ingested. Expectations are that we will load the remaining files into the analytic system by approximately Nov 3 12:00 UTC.

[November 2 23:12 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 120 million event payloads to disk, into 204,000 files. In parallel, we have been loading the resulting files into the analytics data warehouse at approximately 1,900 files per hour, but processing has slowed due to larger files being present. 100% of payloads have been processed to disk, and 173,400 files have been ingested. Expectations are that we will load the remaining files into the analytics system by approximately Nov 3 15:00 UTC.

[November 3 11:23 UTC] Since beginning to load the Kony Server event data up to Oct 30 00:00 UTC, we have processed approximately 120 million event payloads to disk, into 205,000 files. There are approximately 16,000 files remaining, however processing has slowed to 1,200 files per hour due to larger files being present. 100% of payloads have been processed to disk, and 189,400 files have been ingested. Expectations are that we will load the remaining files into the analytics system by approximately Nov 3 20:00 UTC.

[November 4 04:00 UTC] All analytics for the Kony Server feature up to Oct 30 00:00 UTC have processed. Analytics for all other features are current.

[November 6 22:06 UTC] All Kony server data has been loaded into the Analytics system up to Nov 4 04:00 UTC. All Infrastructure and Sync events have been loaded up to Nov 5 04:40 UTC. We have gathered all Kony Server events (approximately 40,000,000) and are processing these to disk. We have re-enabled the automatic collection of event payloads and, in parallel, are continuing to process into files. We are continuing to load files (approximately 39,000 currently) into the analytics data warehouse at a rate of approximately 1,850 files per hour. We are monitoring the event processing and file loading processes until tomorrow and will share a better estimate of progress at that time.

[November 7 23:00 UTC] Kony Server events are continuing to be automatically collected (approximately 24,000,000 in our main queue) and are processing these payloads into files (approximately 16,000,000 events processed in the past 24 hours). We are continuing to load files (approximately 69,000 remaining) into the analytics data warehouse at a rate of approximately 1,850 per hour. We expect most statistics will be loaded by approximately Nov 9 13:00 UTC, but we are adding new files as data collection is on full automation now. We are continuing to monitor event processing and file loading.

[November 8 14:35 UTC] Kony Server events are continuing to be automatically collected (approximately 15,500,000 in our main queue) and are processing these payloads into files (approximately 9,000,000 events processed in the past 15 hours). We are continuing to load files (approximately 100,000 remaining) into the analytics data warehouse at a rate of approximately 1,650 per hour. We expect most statistics will be loaded by approximately Nov 10 17:00 UTC, but we are adding new files as data collection is on full automation now. We are continuing to monitor event processing and file loading.

[November 9 23:10 UTC] Kony analytics are continuing to be automatically collected and processed into files (approximately 1,065,350 messages in our main queue). We are continuing to load files (approximately 159,235 remaining) into the analytics data warehouse at a rate of approximately 1,000 per hour. We expect these statistics to be loaded by approximately Nov 16 12:00 UTC (new files are continuing to be added as data collection is on full automation). We are continuing to monitor event processing and file loading.

[November 13 12:35 UTC] Kony analytics are continuing to be automatically collected and processed into files. We are continuing to load files into the analytics data warehouse (approximately 120,000 files currently and processing at an approximate rate of 1,000 per hour). We anticipate that by Dec 2 00:00 UTC, the majority of these files will be loaded and analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading.

[November 15 12:37 UTC] Kony analytics are continuing to be automatically collected and processed into files. We are continuing to load files into the analytics data warehouse (approximately 114,600 files currently and processing at an approximate rate of 1,000 per hour). We anticipate that by Nov 20 03:00 UTC, the majority of these files will be loaded and analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading.

[November 20 12:30 UTC] Kony analytics are continuing to be automatically collected and processed into files. We are continuing to load files into the analytics data warehouse (approximately 75,270 files currently and processing at an approximate rate of 2,000 per hour). We anticipate that by Nov 22 02:00 UTC, the majority of these files will be loaded and analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading.

[November 22 13:39 UTC] Kony analytics are continuing to be automatically collected and processed into files. We are continuing to load files into the analytics data warehouse (approximately 60,735 files currently and processing at an approximate rate of 7,000 files per day). We anticipate that by Dec 1 13:00 UTC, the majority of these files will be loaded and analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading.

[November 26 20:54 UTC] Kony analytics are continuing to be automatically collected and processed into files. We are continuing to load files into the analytics data warehouse (approximately 20,000 files currently and processing at an approximate rate of 10,000 files per day). We anticipate that by Nov 28 16:00 UTC, the majority of these files will be loaded and analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading.

[November 27 20:41 UTC] Kony analytics are continuing to be automatically collected and processed into files. Analytics up to Nov 27 00:01 UTC should be available. We anticipate that by Nov 28 00:01 UTC, analytics will be available closer to real time loading and we are continuing to monitor event processing and file loading.

[November 28 23:50 UTC] Kony analytics are continuing to be automatically collected and processed into files. Analytics at least up to Nov 28 00:01 UTC should be currently available. Our processing rate has slowed and we are now anticipating that by Nov 29 00:01 UTC, analytics will be available closer to real time loading and we are continuing to monitor event processing and file loading.

[November 30 12:17 UTC] Kony analytics are continuing to be automatically collected and processed into files. Analytics at least up to Nov 30 00:01 UTC should be currently available. We are anticipating that by Dec 1 00:01 UTC, analytics will be available closer to real time loading. We are continuing to monitor event processing and file loading until then.

[January 3 13:22 UTC] Kony analytics are continuing to be automatically collected and processed into files, though our processing rate had slowed due to a significant increase in the number of messages received in the past week. Analytics at least up to Jan 3 12:30 UTC should be currently available. We are anticipating that by Jan 4 14:00 UTC, analytics will be available closer to real time loading (with analytics available within only a few minutes delay) and are continuing to monitor event processing and file loading until then.

[January 4 12:58 UTC] Kony analytics are continuing to be automatically collected and processed into files, though still being processed at a slower rate. Analytics at least up to Jan 3 12:30 UTC should be currently available. We are anticipating that by Jan 5 00:01 UTC, analytics at least up to Jan 4 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 5 12:40 UTC] Kony analytics are continuing to be automatically collected and processed into files, though a significant number of messages have been submitted in the past day, which has further impacted the processing rate. Analytics at least up to Jan 3 12:30 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are reviewing to determine when analytics beyond that date/time will be available and are continuing to monitor event processing and file loading.

[January 8 12:28 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 4 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 12 12:30 UTC, analytics up to Jan 8 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 9 12:20 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 4 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 14 12:30 UTC, analytics up to Jan 9 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 10 12:28 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 4 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 16 12:30 UTC, analytics up to Jan 10 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 11 12:56 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 8 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 16 12:30 UTC, analytics up to Jan 11 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 12 12:39 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 9 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 17 12:30 UTC, analytics up to Jan 12 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 16 14:12 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 11 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 23 12:30 UTC, analytics up to Jan 16 12:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 19 13:42 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 17 00:01 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 26 13:30 UTC, analytics up to Jan 19 13:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 22 15:45 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 19 15:54 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 29 15:30 UTC, analytics up to Jan 22 15:30 UTC will be available. We are continuing to monitor event processing and file loading.

[January 23 12:23 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 20 01:39 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 26 00:01 UTC, analytics up to Jan 23 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 24 12:30 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 19 15:34 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 26 00:01 UTC, analytics up to Jan 24 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 25 12:18 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 22 15:36 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 28 00:01 UTC, analytics up to Jan 25 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 26 14:54 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 23 16:17 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Jan 29 00:01 UTC, analytics up to Jan 26 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 29 12:16 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 26 09:38 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 1 00:01 UTC, analytics up to Jan 29 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 30 12:17 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 27 10:30 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 3 00:01 UTC, analytics up to Jan 30 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[January 31 12:19 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 28 12:09 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 4 00:01 UTC, analytics up to Jan 31 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 1 12:22 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. After further review, analytics at least up to Jan 28 23:20 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 5 00:01 UTC, analytics up to Feb 1 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 2 12:26 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Jan 30 00:31 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 6 00:01 UTC, analytics up to Feb 2 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 5 12:19 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 2 01:24 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 8 00:01 UTC, analytics up to Feb 5 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 6 12:15 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 3 10:54 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 9 00:01 UTC, analytics up to Feb 6 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 7 12:35 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 4 19:30 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 10 00:01 UTC, analytics up to Feb 7 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 8 12:18 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 6 02:16 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 11 00:01 UTC, analytics up to Feb 8 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 9 12:21 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 7 03:26 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 12 00:01 UTC, analytics up to Feb 9 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 12 16:13 UTC] As of Feb 12 12:00 UTC, Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 11 08:14 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 15 00:01 UTC, analytics up to Feb 13 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 13 12:28 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 12 10:55 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 15 00:01 UTC, analytics up to Feb 13 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 14 12:24 UTC] Kony analytics are continuing to be automatically collected and processed into files, though we are still seeing a significant number of messages submitted, which has impacted the processing rate. Analytics at least up to Feb 13 14:00 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 15 00:01 UTC, analytics up to Feb 14 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 15 12:27 UTC] Kony analytics are continuing to be automatically collected and processed into files. We had applied some file processing improvements, which have resulted in an increase in the processing rate over the past few days. Analytics at least up to Feb 14 20:46 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 16 00:01 UTC, analytics at least up to Feb 15 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 16 12:19 UTC] Kony analytics are continuing to be automatically collected and processed into files. We had applied some file processing improvements, which have resulted in an increase in the processing rate over the past few days. Analytics at least up to Feb 15 19:26 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 17 00:01 UTC, analytics at least up to Feb 16 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 20 15:05 UTC] Kony analytics are continuing to be automatically collected and processed into files. We had applied some file processing improvements, which have resulted in an increase in the processing rate over the past few days. Analytics at least up to Feb 20 04:29 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 21 00:01 UTC, analytics at least up to Feb 20 12:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 21 13:09 UTC] Kony analytics are continuing to be automatically collected and processed into files. We have improved the underlying hardware to increase our file processing rate. Analytics at least up to Feb 20 06:24 UTC should be currently available with some analytics after that date/time available, but not the entire set. We are anticipating that by Feb 22 00:01 UTC, analytics at least up to Feb 20 00:01 UTC will be available. We are continuing to monitor event processing and file loading.

[February 23 12:18 UTC] Resolved. We have confirmed that our file processing rate has increased significantly over the last few days following the improvements made to the underlying hardware and additional configuration improvements. As of Feb 22 03:00 UTC, all analytics files in our backlog were able to be loaded into our data warehouse, meaning that all analytics up to that date/time were available. At this time, analytics continue to be available up to the current date/time and we are not observing any delays in processing. We will be continuing to monitor event processing and file loading.

Cloud Management Console Hotfix

Maintenance window: August 21, 2017 04:01 UTC to August 21, 2017 08:00 UTC Impacted Cloud services:

• Cloud Managment Console

  • Fix issue when user generates an integration service (e.g., RDBMS) and adds query binary verb

Impact Level : minor

No significant downtime is expected. The scheduled maintenance is designed for minimal disruption of service availability; however, it is possible for your service(s) to be unavailable for a short period of time during the maintenance window.

Degraded performance for some Clouds in Ireland

Incident window: August 17, 2017 22:03 UTC to August 17, 2017 22:57 UTC Impacted Cloud services:

• Subset of Clouds hosted in Ireland

  • Degraded performance

Impact Level : minor

[22:54 UTC] Our Cloud hosting provider has detected an issue in one of their Ireland datacenters starting at approximately 22:03 UTC. Some performance degradation may be experienced by Kony Clouds hosted in the Ireland region until the data center issue has been addressed. Our provider has determined the root cause and has restored connectivity to some of the affected compute resources, working toward restoring connectivity to the remaining affected instances.

[23:23 UTC] Resolved. Our hosting provider has resolved the issue and connectivity has been restored to all remaining affected instances.

Cloud Management Console and APIs - degraded performance

Incident window: August 11, 2017 15:01 UTC to August 11, 2017 15:32 UTC Impacted Cloud services:

• Cloud Management Console

  • Degraded performance

• APIs

  • Degraded performance

Impact Level : medium

[15:27 UTC] We have detected an increase in latency and error rates for responses from our API servers. We have added additional database indexes to improve performance in the long-term. We are continuing to monitor the issue.

[16:02 UTC] Resolved. System performance has stabilized. We are continuing to monitor for this issue and are continuing to work on preventing recurrence long term.

Application publish failures for Clouds in US Virginia

Incident window: August 10, 2017 10:15 UTC to August 10, 2017 14:30 UTC Impacted Cloud services:

• MobileFabric Clouds in US Virginia

  • High error rate for application publishes

Impact Level : high

[16:47 UTC] Resolved. Between 10:15 and 14:30 UTC, we observed a high number of application publishes failing for customers whose MobileFabric Clouds are hosted in US Virginia. We traced the issue traced back to our Cloud hosting provider, who has since resolved the underlying issue. If you experienced a publish failure during the incident window, you can now retry. Applications that were already published were not affected by this incident.

Cloud Management Console and APIs - degraded performance

Incident window: August 09, 2017 15:00 UTC to August 09, 2017 15:30 UTC Impacted Cloud services:

• Cloud Management Console

  • Degraded performance

• APIs

  • Degraded performance

Impact Level : medium

[15:29 UTC] We have detected an increase in latency and error rates for responses from our API servers. We are investigating the issue.
[16:02 UTC] Resolved. System performance has stabilized. We are continuing to monitor for this issue and are continuing to work on preventing recurrence long term.