Discussions
GREEN / BULK API Exports Backlogged / POD 1 / RESOLVED
Our Cloud Operations Team is currently investigating an incident impacting Bulk API Exports on POD1. We do not currently have an ETA for resolution. The next update is scheduled for 10:00 am EDT (UTC -4)
====================================
**Update**
Tuesday, October 14th, 9:59 am EDT (UTC -4)
Our Cloud Operations Team is still actively investigating this incident, but we do not have an ETA at this time. The next update will be around 11:00 am EDT (UTC-4)
====================================
**Update**
Tuesday, October 14th, 11:00 am EDT (UTC -4)
Our Cloud Operations Team continues to investigate this incident. The next update will be around 12:00 pm EDT (UTC-4)
====================================
**Update**
Tuesday, October 14th, 12:00 pm EDT (UTC -4)
Our Cloud Operations Team is still currently investigating the incident. The next update will be around 1:00 pm EDT (UTC-4)
====================================
**Update**
Tuesday, October 14th, 1:00 pm EDT (UTC -4)
Our Cloud Operations Team continues to investigate this incident. The next update will be around 2:00 pm EDT (UTC-4)
====================================
**Update**
Tuesday, October 14th, 2:00 pm EDT (UTC -4)
Our Cloud Operations Team have identified the problem and are currently working towards a resolution. The next update will be around 3:00 pm EDT (UTC-4)
====================================
**Update**
Tuesday, October 14th, 3:00 pm EDT (UTC -4)
Our CloudOps Team have applied a fix which is currently decreasing the backlog. While we currently do not have an ETA for when the backlog will be completed, the next update will be around 4pm EDT (UTC -4)
====================================
**Update**
Tuesday, October 14th, 4:00 pm EDT (UTC -4)
Our CloudOps Team have applied the fix which is still currently decreasing the backlog queue. While we currently do not have an ETA for when the backlog will be completed, the next update will be around 5pm EDT (UTC -4)
====================================
**Update**
Tuesday, October 14th, 4:17 pm EDT (UTC -4)
This incident was fully resolved as of 4:17 PM EDT ( UTC -4)
After analysis by our support teams, it was determined that the incident was the result of a software bug of an Oracle Program. Information related to the incident has been passed on to our Product Engineering team. Once Product Engineering confirms they have a resolution to the issue, it will be deployed to the applicable Oracle Programs for your Eloqua service. No ETA for resolution is available at this time. Oracle is also reviewing the monitoring, alerting and standard operating procedures related to the incident. After these reviews are completed, additional appropriate corrective actions identified during the reviews will be taken, including deployment of the appropriate patch or release when available.