Experian Digital - Look Who's Charging Status

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.

Resolved: Traffic was returned to our primary environment at 8:00 pm AEDT on Friday, 23 October. Latency returned to normal, and we have observed no further issues during close monitoring since then.

The issue affecting our primary Redis service has been resolved with assistance from Microsoft support. Service remained available through our secondary environment, with slightly higher latency during this period.

We are awaiting Microsoft’s root cause analysis and post-incident review and will share further details once available.

Identified: There is an ongoing issue on our primary Redis Cache due to which traffic has been failed over to our disaster recovery site. We are investigating the Redis issue with Azure.