Learnosity kesinti geçmişi

1. 26 Ekim 2026 18:05 UTCinvestigating

   17:50 UTC olarak, tüm bölgelerdeki Item Havuzlarını etkileyen sorunlar yaşıyoruz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 26 Ekim 2026 18:34 UTCinvestigating

   18:30 UTC olarak, Item Havuzları oluşturma ve düzenleme yaparken bozulan performansı araştırıyoruz. Ayrıca, yerel Cihaz Değerlendirme paketlerinin oluşturulması ve düzenlenmesini etkileyen somut olmayan bir konuyu da araştırıyoruz. Yazarda diğer tüm API'ler, değerlendirme ve analitik yığınlar normalde çalışıyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 26 Ekim 2026 19:01 UTCinvestigating

   19:00 UTC olarak, Item Havuzları veyax Local Cihaz Değerlendirme paketlerini oluştururken lisansüstü performansı incelemeye devam ediyoruz. Yazarda diğer tüm API'ler, değerlendirme ve analitik yığınlar normalde çalışıyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

4. 26 Ekim 2026 19:31 UTCmonitoring

   19:30 UTC olarak, Item Havuz ve Yerel Cihaz Değerlendirme yaratımı yaklaşık 30 dakika boyunca normal olarak görüldü. Artık istikrar sağlamak için başka bir izleme süresine gireceğiz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

5. 26 Ekim 2026 20:10 UTCresolved

   20:10 UTC olarak, Item Havuz veya Yerel Cihaz Değerlendirme paketi oluşturma veya güncelleme ile daha fazla sorun görmedik. Bu olayı çözüyoruz ve bozulan performansın kök nedenini araştırmaya devam edeceğiz. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 20 Ekim 2026 14:16 UTCinvestigating

   13:20 UTC olarak, ABD-Doğu-1 bölgesinde gelişmiş Math Scoring hizmetimizle puanlama gecikmelerini görmeye başladık. Hiçbir veri kaybı gözlemlenmedi ve tüm seanslar sonunda alındı. Bir knock-on etkisi olarak, Data API Scoring endpoint intermittent kullanılabilirlik sorunları yaşıyor. Hiçbir yazar veya değerlendirme teslimatı etkilenmiştir. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 20 Ekim 2026 15:04 UTCinvestigating

   15:00 UTC olarak, gelişmiş Math Scoring servisimizin kısa ömürlü degraded performansını araştırıyoruz, ancak bir saatten fazla önemli hataları veya gecikmeleri görmedik. Puanlama bekleyen arka seanslar hızlı bir şekilde temizlenir ve başvurular normalde puan almaya devam eder. Diğer tüm API'ler etkilenmez. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 20 Ekim 2026 15:51 UTCmonitoring

   15:45 UTC olarak, mitigation önlemleri teslim sırayı net bir şekilde tuttu ve skor normalde çalışmaya devam etti. Emekli performans döneminde alınan kehanetler yakalandı ve hiçbir veri kaybedilmedi. Diğer tüm API'ler operasyonel olarak kalır. Kök nedenini incelemeye devam ediyoruz ve soruşturmamız tamamlandıktan sonra bir olay sonrası paylaşacağız. Bu arada, olayı kapatmadan önce devam eden istikrarı doğrulamak için daha fazla izleme süresine giriyoruz.

4. 20 Ekim 2026 18:17 UTCresolved

   18:00 UTC olarak, daha fazla sorun olmadan uzun bir süre sonra, bu olayı ABD-Doğu-1'de Gelişen Math Scoring'i etkileyen bir çözümle çözdük. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

5. 27 Ekim 2026 13:27 UTCpostmortem

   ## Etkilenen Sistemler ve Bölgeler 20 Ekim 2026'da, Learnosity, ABD-Doğu-1'de Geliştirilmiş Matematik skorunu etkileyen başarısızlıkları deneyimledi ve intermittent talep ediyor. Müşteri etkisi yaklaşık 13:06 UTC'de başladı ve yaklaşık 41 dakika süren 13:47 UTC'de sona erdi. Etkilenen puanlama istekleri normal işlem zamanlarından daha uzun yaşadı ve Data API puanlama uç noktası hataları geri aldı. Malzemeler API'si aracılığıyla kaydedilen seanslar için, etkilenen puanlama talepleri sıralandı ve geri alındı, skor başarısızlıklarından ziyade gecikmiş puan kullanılabilirliği elde etti. Diğer bölgelerdeki matematik soruları ve hizmetleri olmadan değerlendirmeler etkilenmedi. ## Araştırmamız beklenmedik derecede yüksek işleme süreleri ile sonuçlanan belirli bir puanlama talebi tespit etti. Bu, diğer puanlama taleplerini işlemek için mevcut kapasiteyi azalttı, gecikmelere ve geçici zamana yol açtı. Sorun, genel istek hacminde beklenmedik bir artış yerine belirli puanlama girişlerinin nasıl işlendiği ile ilişkilendirildi. ## Karar Scoring performansı 13:47 UTC tarafından normale döndü. 15:12 UTC'de, Learnosity mühendisleri, diğer müşteriler için skorlama işlemlerinin etkisini önlemek için daha fazla trafik izolasyonu uyguladılar. # ## Önleme Learnosity, gereksiz kaynak tüketimini azaltmak ve etkilenen skorlama taleplerinin düzeltilmesi için değişiklikler uyguladı. Daha fazla gelişme, puanlama talebini doğrulamayı güçlendirmek, işleme korumalarını geliştirmek ve bireysel puanlama iş yüklerini daha geniş hizmeti etkilemelerini sağlamaktır. Ek izolasyon önlemleri, bu gelişmeler tamamlandığında ve onların etkinliği doğrulanacaktır.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 8 Ekim 2026 13:40 UTCinvestigating

   13:00 UTC olarak, tüm bölgelerde en son LTS'ye günbatımı API versiyonlarını yeniden ele geçiriyoruz. Bu, 2026 Mart'ta Yaşamın Sonu'na ulaşan v2024.1.LTS'ye hala karışan çok az sayıda müşteriyi etkiler. Başka API versiyonları etkilenmez. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 8 Ekim 2026 13:47 UTCinvestigating

   13:40> UTC olarak, v2024.1.LTS versiyonlarını ve API'leri önbellekler güncelleme olarak erişilebilir hale getiriyoruz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 8 Ekim 2026 14:20 UTCinvestigating

   14:00 UTC olarak, v2024.1.LTS, ABD-Doğu-1 (VA) ve ABD-West-2 (OR) de dahil olmak üzere AMER bölgelerindeki son LTS versiyonuna başarıyla geri dönüyor. Tüm API'ler bu bölgelerde erişilebilir olmalıdır. Şu anda EMEA ve APAC bölgelerinde yankılanıyoruz. Aktif API versiyonlarına doğrudan erişim operasyonel kalır. Bu sorun şu anda sadece 2026 Mart'ta EOL'e ulaşan günbatımı ve APAC bölgelerindeki müşterilerin mikro setini etkiliyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

4. 8 Ekim 2026 15:15 UTCresolved

   15:00 UTC olarak, v2024.1.LTS tüm bölgelerde başarılı bir şekilde tekrarlanıyor. Bu EOL/sunset sürüm dizesini kullanarak tüm API'lere erişmek gerekir. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

5. 28 Ekim 2026 22:14 UTCpostmortem

   ### Etkilenen Sistemler ve Bölgeler 8 Ekim 2026'da, Learnosity, ABD Virginia, Avustralya ve İrlanda bölgelerinde emekli API versiyonlarını belirten geçici API hataları yaşadı. Bu versiyon 2026 Mart'ta Yaşama ulaştı Günbatımı sonrasında, etkilenen istekler otomatik olarak en son uzun vadeli destek \(LTS\) sürüme yönlendirilmelidir. Bunun yerine, bazı iade sunucu hataları. Müşteri etkisi yaklaşık 00:14 UTC'de başladı ve bölgeye değişen 15:08 UTC'ye kadar geçici olarak devam etti. Sadece üretim sunucularının bir kısmı etkilendi, bu yüzden bu sürümü belirten tüm istekler başarısız oldu. # # ## Olay 8 Ekim platform serbest bırakılması sırasında eksik bir yapılandırma güncellemesine neden oldu, bu da ‘v2024.1.LTS’i emekli etti. Güncellenen sürüm haritalanması, üretim yapılandırma sunucularını güncellemek için gerekli bir salıverme aşamasında doğru olmasına rağmen. Sonuç olarak, bazı üretim sunucuları kaldırıldı API versiyonlarına yönlendirilen eski bir haritayı korudu. Mevcut sürümümüz API versiyonlarının mevcut olduğunu doğruladı ancak her üretim bölgesinde emekli sürümlerin doğru bir şekilde yönlendirildiğini doğrulamadı. Sonuç olarak, tutarsızlık dağıtım sırasında tespit edilmedi. # # ## Karar Öğrenme mühendisleri, eski sürüm haritasını ve restore hizmetini etkilenen üretim sunucularında, bölge tarafından yeniden üreterek tespit etti. 15:08 UTC'ye göre, doğrulama doğru versiyon haritalamanın tüm kontrol bölgeleri ve talepleri doğru şekilde ele alındığını doğruladı. Olay resmi olarak 15:48 UTC'de çözülmüştü. ### Önleme Öğrenmeler, benzer yapılandırma tutarsızlıklarını önlemek için serbest bırakılması ve geçerlileştirme prosedürlerine yönelik gelişmeler uyguluyor. Bunlar, tüm üretim yapılandırma sunucularının doğru salıverme sürümlerini çalıştırdığını, yapılandırma güncelleştirmelerini doğrudan dağıtım sürecine entegre ettiğini ve her bölgedeki emekli API sürümlerini doğru bir şekilde doğrulamayı doğrulamalarını içerir. Ayrıca, bu belirli hata sınıfını daha önce tespit etmek ve yenileme sunucularının eski konfigürasyonları koruduğunu tespit etmek için uyarı geliştiriyoruz. Bu önlemler, bölge genelinde tutarlı dağıtımları sağlamak, müşterileri etkilemeden önce yapılandırma diskrepancies tespit etmek ve kurtarmanın benzer konularda gerçekleşmesi gerekir.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 2 Ekim 2026 18:08 UTCinvestigating

   16:45 UTC olarak, ABD-Doğu-1 bölgesinde gelişmiş Math Scoring hizmetimizle çok düşük puanlama gecikmeleri yaşadık. Tüm seanslar alındı ve veri kaybı olmadı. Başka API'ler etkilenmez. Bu hizmetle sınırlı devam eden gecikmeleri araştırıyoruz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 2 Ekim 2026 18:30 UTCidentified

   18:30 UTC olarak, gelişmiş Math Scoring hizmeti için bir ölçeklendirme sorunu tespit ettik ve sorunu çözmek için çalışıyoruz. Tüm seanslar veri kaybı olmadan yakalamaya devam ediyor ve diğer tüm API normal olarak çalışıyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 2 Ekim 2026 19:10 UTCmonitoring

   19:00 UTC olarak, bir süredir gelişmiş Math Scoring servisinde gecikmeler görmedik ve şimdi bir izleme aşamasına gireceğiz. Sorunu çözmeden 30 dakika boyunca izlemeye devam edeceğiz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

4. 2 Ekim 2026 19:52 UTCresolved

   19:45 UTC olarak, ABD-Doğu-1 bölgesinde gelişmiş Math Scoring'i etkileyen sorunu çözdük. Tüm API ve hizmetler normalde çalışıyor. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

5. 27 Ekim 2026 01:24 UTCpostmortem

   # **Affected Systems and regions** 2 Ekim 2026'da, Learnosity, ABD-Doğu-1'deki matematik soru tiplerini etkileyen geçici puanlama hataları ve zaman aralıkları yaşadı. Müşteri etkisi yaklaşık 16:34 UTC'de başladı ve 18:47 UTC'de sona erdi, yaklaşık 2 saat ve 13 dakika. Etkilenen istekler başarısız olmadan 40 saniyeye kadar gecikme yaşayabilir. Diğer bölgeler etkilenmedi. # **Investigation** Olay matematik puanlama hizmeti talep edildiğinde mevcut kapasiteyi aştı. Daha önceki bir olayı takip eden kapasite ve ölçeklendirme iyileştirmeleri olmasına rağmen, hizmet, daha fazla örneği geçici hale getiren ağ konfigürasyonunda ek bir limitle karşılaştı. Etki, daha uzun süredir işgal edilen tahminlerle bileşiklenmiştir çünkü zaman limitleri ağır yük altında güvenilir bir şekilde uygulanmadı. Birlikte, bu koşullar hizmeti talep etmek için yeterince ölçeklendirmeden engelledi. # **Resolution** Learnosity mühendisleri, puanlama hizmetini ek ölçeklendirme kapasitesi ile bir ağ yapılandırmasına sağlayarak ve her örneke ayrılan hesap kaynaklarını artırarak restore etti. Bu değişiklikler, 18:47 UTC tarafından açıklanan puanlama hataları ile hizmetin geri dönmesine izin verdi. # **Provention** Learnosity, sabit yük altında yavaş hesaplamaları güvenilir bir şekilde sonlandırmak için hesaplama süresini güncelledi. Sağlık kontrolleri de gereksiz örnek değiştirmeyi önlemek için hesaplama işleminden ayrı olmuştur. Servis şimdi ek hesaplama ve ağ kapasitesi ile çalışır. Daha fazla mimari gelişme, ağ kapasitesinin gelecekteki ölçeklendirmeyi önlemeye devam ediyor ve alışılmadık yavaş hesaplamaların etkisini azaltmak için daha kısa hesaplama zaman limitlerini değerlendiriyoruz.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 11 Eylül 2026 18:19 UTCinvestigating

   17:00 UTC olarak, şu anda ABD-Doğu-1 bölgesinde puanlama ile küçük geçici sorunları araştırıyoruz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 11 Eylül 2026 18:30 UTCinvestigating

   18:30 UTC olarak, tüm APIler operasyonel olarak kalır ve skor verimliliğini izliyoruz. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 11 Eylül 2026 19:42 UTCidentified

   19:30 UTC olarak, bunu sadece üç gelişmiş matematik soru tipinin puanlanmasıyla bir sporadik problem olduğunu doğruladık. Bu skorlamalar yeniden denemede başarılı olur ve başka API'ler etkilenmez. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

4. 11 Eylül 2026 20:53 UTCmonitoring

   20:45 UTC olarak, ilk skorlama Çocuğa istek ve retries'in kullanımını geliştirdik ve şimdi 60 dakikalık bir izleme aşamasına gireceğiz. Tüm APIler normalde çalışmaya devam ediyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırmaya devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

5. 11 Eylül 2026 21:44 UTCresolved

   21:45 UTC olarak, gelişmiş Math Scoring sorusu tür yanıtlar ABD-Doğu-1 bölgesinde normalde puanlanıyor ve tüm API'ler normalde çalışıyor ve bu olayı kapatıyoruz. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

6. 27 Ekim 2026 01:23 UTCpostmortem

   # **Affected Systems and regions** 11 Eylül 2026'da, Learnosity, ABD-Doğu-1'deki matematik soru tiplerini etkileyen geçici puanlama hataları ve zaman aralıkları yaşadı. Müşteri etkisi yaklaşık 17:00 UTC'de başladı ve 21:45 UTC'de sona erdi, yaklaşık 4 saat ve 45 dakika. Diğer soru türleri normalde puan almaya devam etti ve diğer bölgeler etkilenmedi. Çoğu başarısız istek, retried edildiğinde başarılı oldu. # **Investigation** Olay, önceki haftalarda talep edilen artıştan sonra matematik puanlama hizmetinde yetersiz kapasiteye neden oldu. Servis maksimum sayıda örneke ulaştı ve yükü karşılamak için daha fazla ölçeklenemedi. Bu, örneğin sınırlı hesaplama kaynakları tarafından bileşiklendi ve daha uzun süre işgal edilen örnekleri daha yavaş hesaplamalar. Ağır yük altında, hesaplama süresi sınırı güvenilir bir şekilde uygulanmadı ve yoğun durumlarda sağlık kontrollerini başarısız olabilir ve değiştirilmesi, mevcut kapasiteyi daha da azaltır. # **Resolution** Öğrenme mühendisleri, çalışan örneklerin sayısını artırmak ve maksimum örnek sınırı artırmakla hizmet etti. Normal puanlama işlemleri 21:45 UTC tarafından yeniden başladı ve kalan tüm kuyruk puanlama talepleri 23:17 UTC tarafından işlendi. 14 Eylül'de, hesaplama kaynaklarını artırmak, otomatik ölçeklendirmeyi geliştirmek ve gereksiz örnek değiştirmeyi azaltmak için ek konfigürasyon değişiklikleri kullanılmıştır. # **Provention** Learnosity, skor kapasitesini artırdı, örnek sınırları yükseltti ve işlemci kullanımına dayanan otomatik ölçeklendirme geliştirdi. Sağlık kontrolleri, yoğun örneklerin yanlış olarak sağlıksız olarak tanımlanmasını engellemek için hesaplama işleminden ayrılır. Ayrıca kaynak kullanımı, yanıt süreleri ve puanlama hataları için zaman limiti ve genişleyen izleme ve uyarılama zamanı geliştirdik. Daha fazla çalışma ağ ölçeklendirme kapasitesini güçlendirmek ve daha kısa hesaplama zaman limitlerini değerlendirmek için otoyoldur.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 24 Temmuz 2026 12:16 UTCinvestigating

   ABD-West-2 (OR) bölgesini etkileyen devam eden bir AWS sorununun farkındayız, bu da Öğrenmelerin İzin Vermeye Yardımcı Olduğunda Geçici Bağlantı Sorunlarına neden olabilir. Durumu aktif olarak izliyoruz ve mevcut oldukları gibi güncelleştirmeler sağlayacaktır. Bu zamanda, Learnosity müşterilerinin etkisi kısa ve aralıklı ve yazarları ile sınırlı. Değerlendirmeler ve diğer API'ler normalde davranıyor. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak araştırıyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecektir.

2. 24 Temmuz 2026 12:28 UTCmonitoring

   11:02 UTC olarak, Learnosity, Learnosity yazarı sitesine eriştiğinde kısa süreli uyarıları görmeye başladı. Başka bir işlevsellik etkilenmedi ve Learnosity uyarıları 11:11 UTC'de durduruldu. 11:40 UTC'de, AWS ABD-West-2 (OR) bozulduğunu bildirdi. 11:56 UTC'de, AWS sistemlerinin kurtarıldığını bildirdi. Learnosity Support ve Systems Engineering takımları konuyu aktif olarak izlemeye devam ediyor ve mümkün olduğunca kısa sürede bir güncelleme ve kararla takip edecek.

3. 24 Temmuz 2026 12:35 UTCmonitoring

   12:30 UTC'de, AWS konuyu tespit ettikleri ve düzeltdiklerini ve bu kurtarmanın devam ettiğini bildirdi. Learnosity Support ve Systems Engineering takımları konuyu 30 dakika daha takip edecek ve en kısa sürede bir güncelleme ve kararla takip edecektir.

4. 24 Temmuz 2026 13:02 UTCresolved

   13:00 UTC olarak, bu sorunu çözdük. AWS sistemleri kurtarılır ve Bilgilendirme yazarı 50 dakika boyunca etkilenmemiştir. Learnosity Support and Systems Engineering takımları, kök neden analizi tamamlanmış ve bir sonraki adımları veya gerekli önleyici önlemleri sonlandırdığımız bir post mortem ile takip edecektir. Lütfen herhangi bir sorunuz veya endişeniz varsa dışarı çık.

5. 24 Temmuz 2026 13:03 UTCpostmortem

   ### Etkilenen Sistemler ve Bölgeler 2026-07-24'de, Learnosity kısa süreli yayınlar, AWS US-West-2 \(OR\) bölgesinde [aTYS / Sağlık/status?event=arn:aws:health:us-west-2:event/MULTIPLE SERVICES / AWS MULTIPLE SERVICE Öğrenme müşteri etkisi yaklaşık 11:02 UTC'de başladı ve 11:11 UTC'de sona erdi. AWS daha sonra remediasyon tamamladı ve 12:12 UTC'de bölgesel olayı resmen kapattı. Öğrenme müşterileri için mümkün olan toplam etki yaklaşık 9 dakikaydı. # # ## Learnosity 11:02 UTC'de OR bölgesinde hizmet etkilendi ve hemen bir soruşturma başlattı. İlk soruşturma, bir Öğrenme servisi bozulmasının kanıtı bulamadı. Daha fazla soruşturma, Öğrenme Yazar sitesine erişimi etkileyen zaman aralıkları tespit etti. Learnosity AWS ile bölgedeki ağ altyapılarını etkileyen bir sorun tespit edildi ve remediasyon başladı. # # ## Karar Learnosity yazarın sitesini etkileyen zaman aralıkları 11:11 UTC tarafından durduruldu ve AWS konuyu 11:15 UTC ile etkin bir şekilde çözdü. AWS 11:59 UTC tarafından çözülebilen kısa bir yeniden hayal kırıklığı olayı bildirdi ve olayı 12:12 UTC'de resmen kapattı. ### Önleme Öğrenme sistemleri bu olaya katkıda bulunmadı. İç izleme ve uyarı beklenen gibi davranır.

Resmî olay güncellemesinden otomatik olarak çevrilmiştir.

1. 17 Nisan 2026 16:06 UTCinvestigating

   As of 16:00 UTC, we are currently experiencing a slowdown in availability of newly submitted submitted session results in the us-east-1 region. There is no data loss, all saves and submissions are being queued as designed, and the assessments stack remains operational. Delays may currently be experienced using the Data API to fetch session results, and the Reports API to display results. Other workflows that rely on the synchronous use of Data API results may also be affected. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 17 Nisan 2026 16:21 UTCidentified

   As of 16:20 UTC, Learnosity has increased database performance and we are processing queued sessions rapidly. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 17 Nisan 2026 16:28 UTCmonitoring

   As of 16:25 UTC, we have resolved the slowdown in processing session results and all sessions are being scored normally. We will continue to monitor for a further 30 minutes before closing this incident report. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 17 Nisan 2026 17:58 UTCresolved

   As of 16:55 UTC, we are have resolved the degraded performance issue affecting availability of session data in us-east-1. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

5. 4 Mayıs 2026 17:23 UTCpostmortem

   ### Affected Systems and Regions On 2026-04-17, Learnosity experienced a service degradation impacting availability of newly submitted session results for a small subset of customers in US-East-1. The issue began at approximately 13:54 UTC and was resolved at 16:24 UTC. The total duration of customer impact was approximately 2.5 hours. ### Investigation Service degradation was detected following the accumulation of submitted sessions in the async scoring queue, This was caused by elevated CPU utilization when heavy load coincided with a background data migration task that had been running for several days on the affected EC2 instance. This reduced message processing throughput, leading to queueing of sessions.  ### Resolution Learnosity CloudOps engineers responded by scaling session processing node EC2 instances, and corresponding database proxies, to maximum allowable capacity. The migration task was also stopped, which further reduced CPU pressure and allowed message processing throughput to recover. The session scoring backlog was fully cleared by 16:24 UTC. ### Prevention Learnosity is implementing the following measures to mitigate: * Pre-flight health checks and safeguards are being introduced to prevent migration tasks from running during busy periods of production usage. * Enhanced monitoring is being applied to detect backlog growth and database contention, and apply remedial action more quickly

1. 16 Nisan 2026 14:08 UTCinvestigating

   As of 13:30 UTC, we are currently experiencing slow downs affecting the Live Progress report in the us-east-1 region. Atypical use of eventbus may also be affected, such as custom reports/implementations. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 16 Nisan 2026 15:23 UTCresolved

   As of 14:30 UTC, the Live Progress report event degradation issue in the us-east-1 region has been resolved. Additional capacity processed the event load and these systems are operating normally. Brief additional latency during this scaling may have been introduced for users of Learnosity's premium Firehose feature, but we've seen no evidence that this affected customers. This, too, was resolved once scaling was complete. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

3. 4 Mayıs 2026 14:39 UTCpostmortem

   ### Affected Systems and Regions On 2026-04-16, Learnosity experienced a service degradation impacting the Live Progress report for a small subset of customers in the us-east-1 region. The issue began at approximately 13:12 UTC and was resolved at 14:40 UTC. The total duration of customer impact was approximately 88 minutes. ### Investigation The issue was detected following elevated error rates on the load balancer serving the eventbus service. Investigation determined that an unhealthy condition within the EC2 instances led to elevated CPU utilization and memory pressure within the Auto Scaling Group, resulting in application instability and repeated service restarts. Inconsistent recovery caused traffic to concentrate on a subset of hosts, further elevating error rates. A secondary effect of the instability was increased request pressure on downstream dependencies. ### Resolution Service was restored by stabilizing the affected EC2 instance and restoring consistent application availability across the Auto Scaling Group. Load distribution normalized once all instances returned to a healthy state. ### Prevention Learnosity is implementing the following measures to mitigate: * Improve service startup and dependency handling to ensure consistent recovery behavior * Review resource thresholds to reduce the likelihood of similar instability * Enhance monitoring to detect and respond more quickly to similar conditions

1. 4 Şubat 2026 18:34 UTCidentified

   As of 18:30 UTC, we are currently experiencing an issue affecting assessment delivery in VA (us-east-1). Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 4 Şubat 2026 18:55 UTCmonitoring

   As of 18:52 UTC, the Learnosity System Engineering team has put a fix in place. We will continue to monitor for some time to ensure a stable recovery, but all services are operational again. Learnosity Support and Systems Engineering teams will continue to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

3. 4 Şubat 2026 19:15 UTCresolved

   As of 19:12 UTC, traffic has returned to normal and everything remains stable. We have resolved the incident affecting assessments in VA (us-east-1). Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

4. 10 Şubat 2026 17:08 UTCpostmortem

   ### **Affected Systems and Regions** On 2026-02-04, Learnosity experienced an availability incident impacting Questions API access for customers in the AMER region. The issue began at approximately 18:02 UTC and was formally declared resolved at 18:51 UTC. The total duration of customer impact was approximately 49 minutes. ### **Investigation** The issue was first detected when the Items API attempted to initialize the dependent Questions API. The incident was traced to a misconfiguration within the content delivery network servicing the AMER region, causing a SSL certificate error.. During a certificate management task, the distribution responsible for serving [_questions.learnosity.com_](http://questions.learnosity.com) was configured with an SSL certificate that did not match the _\*.learnosity.com_ domain nomenclature. This caused browsers and client systems to reject connections to the affected subdomain. ### **Resolution** Once the issue was identified, the response team updated the affected distribution to use the correct SSL certificate. Service was fully restored after the change was completed. ### **Prevention** Learnosity is strengthening certificate deployment and validation processes to ensure that domain mappings are verified prior to rollout. Additional safeguards have been added to prevent cross-domain certificate assignments and to improve monitoring for sudden traffic drops that may indicate certificate-related failures.

1. 12 Ocak 2026 17:06 UTCinvestigating

   As of 4:30 UTC, we are currently investigating an issue that may result in temporary session unavailability for a small number of US-only customers. We can confirm that no session data has been lost, and we are working to restore the affected sessions as quickly as possible. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 12 Ocak 2026 17:52 UTCidentified

   As of 5:30 UTC, we've identified and corrected a load balancing configuration affecting database reads and writes for a very small number of US-only customers with consumers in the US-East-1 region. - All new sessions will behave as expected. - Read requests seeking data on sessions created prior to 23:00 UTC yesterday will also now behave correctly. - We are working on restoring sessions recently affected While all APIs continue to function normally, this update identifies service areas that may temporarily have limited access to recently saved or submitted sessions. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 12 Ocak 2026 19:10 UTCresolved

   As of 7:00 UTC, we've concluded our monitoring and confirmed that all new requests are behaving as expected. We are closing this record and will continue to work with affected customers directly to confirm that all recent sessions are accessible. Please reach out if you have any questions or concerns.

1. 20 Ekim 2025 14:53 UTCmonitoring

   Learnosity services in VA are continuing to be partially impacted by the major AWS outage. AWS first reported the incident at 7:11 UTC As of 14:50 UTC they are continuing to work on its full resolution, but have again set their impact level to "Degraded". The AWS Health Status dashboard where updates are being posted by the AWS team can be found here: https://health.aws.amazon.com/health/status Overall, the error rate has fallen and has stayed below what we saw earlier in the day and we have been successful in slowly scaling up the infrastructure, but we're still seeing some issues stemming from the the ongoing AWS outage as we attempt to bring online some new instances, and we have begun to see an uptick in errors. These have included errors associated with Data API, Feedback Aide, and the delivery of adaptive assessments, delays in scoring and video encoding, as well as other smaller spikes across different systems. While the overall error rate remains low, Learnosity Support and Systems Engineering teams are actively monitoring the outage and manually intervening where possible to mitigate the issues we're facing. In spite of our best efforts it is likely that the APIs may not be fully operational in VA until AWS's service is fully restored to normal operation, but we are taking every step within our power to try to minimize the disruption to our services.

2. 20 Ekim 2025 15:30 UTCinvestigating

   As of 15:25 UTC, we are seeing increasing error rates. Data API is the most affected service at the moment and we are seeing an increase in scoring delays, but we are continuing to score incoming messages to the best rate our current capacity allows. AWS is still reporting a severity of "Degraded", but now with an increased count of 81 affected services. Learnosity Support and Systems Engineering teams are continuing to monitor the issue, and will continue our mitigation efforts wherever possible.

3. 20 Ekim 2025 18:13 UTCmonitoring

   As of 19:10 UTC, we are beginning to see errors rates diminish and some Learnosity services are beginning to scale again. AWS is still reporting a severity of "Degraded" with problems to 104 of their services in us-east-1. Learnosity Support and Systems Engineering teams are continuing to monitor and manually intervene when possible to mitigate the effects of the outage.

4. 20 Ekim 2025 19:02 UTCmonitoring

   As of 20:00 UTC, the error rate has continued to drop, systems remain scaled and the backlogs of scoring messages continues to drop. AWS is still reporting 109 impacted services and a severity of "Degraded" Learnosity Support and Systems Engineering teams are continuing to monitor the issue and are manually adjusting the infrastructure where needed to ensure stability.

5. 20 Ekim 2025 19:32 UTCmonitoring

   As of 19:30 UTC, the error rate has fallen to 0.1% and continues to fall, we continue to steadily process the backlog of scoring messages. As of their latest update AWS has downgraded the severity of outage to "Impacted" but still list 109 services as affected. Learnosity Support and Systems Engineering teams are continuing to actively monitor the issue, and will follow on with an update and resolution as soon as possible.

6. 20 Ekim 2025 20:44 UTCmonitoring

   As of 20:40 UTC, the error rate remains low, the infrastructure is scaled to meet demand, and the scoring queues are empty and new submissions are being processed as they come in. All services are operational and we are processing the remaining backlog of messages from the incident. AWS still lists 93 affected services and a severity of "Impacted". Learnosity Support and Systems Engineering teams are continuing to monitor the issue, but at the moment all systems are fully operational.

7. 20 Ekim 2025 21:35 UTCresolved

   As of 21:30 UTC, all systems keep operating normally, so we are resolving the status page about the AWS outage affecting Learnosity Services in the VA (us-east-1) region. Learnosity Support and Systems Engineering teams will continue to monitor the systems closely while AWS continues to work on the issues on their side. Please reach out if you have any questions or concerns.

1. 20 Ekim 2025 10:11 UTCmonitoring

   AWS is going through late-stage recovery of a major outage in US-East-1 bringing down most of their services. Learnosity APIs were stable and unaffected in isolation, but some impact cascaded to Learnosity (such as availability of assets from CloudFront). The full extent of the incident is unknown at this time. NOTE: Up until the time of this writing (10:05 UTC), this included impact to sign-in services that prevented us from accessing our StatusPage. We immediately posted banner notifications in our Support Portal, and those banners will remain visible until we've been able to verify that service has been restored for sufficient time. Incident History: As of 7:00 UTC, AWS experienced a major outage. While Learnosity APIs were fully operational, some Learnosity services use AWS and were affected. These included access to our Support ticketing system (the Learnosity-hosted Help guides were unaffected), and availability of CloudFront-hosted assets, but other systems may have been impacted as well. As of 10:00 UTC, AWS has restored services and access to Learnosity-adjacent features is becoming available relatively quickly. Learnosity Support will monitor AWS for a further 30 minutes before calling this issue resolved. We will follow on with an update and resolution at that time, or sooner.

2. 20 Ekim 2025 11:23 UTCresolved

   As of 11:20 UTC, AWS services appear to have been stable for approximately an hour. Learnosity APIs--including services affected by the AWS outage (such as CloudFront)--appear to be fully operational. At this time we are labeling this issue resolved. Learnosity Support and Systems Engineering teams will continue to investigate impact from this incident and follow up with a post mortem once we hear from AWS. Please reach out if you have any questions or concerns.

1. 2 Ekim 2025 21:34 UTCinvestigating

   As of 21:15 UTC, Learnosity APIs are being impacted by a temporary outage from our Math partner, Desmos. Authoring or Editing content with Desmos questions or features, or initializing assessments that contain Desmos questions or features, can prevent the Author API or Items API from initializing. Specific reports that display question content, such as the Session Detail by Item report, can also fail to initialize Learnosity APIs are not otherwise impacted, so content that does not include Desmos features are not affected. Until we learn more, we will list APIs that may experience knock-on effects from this temporary Desmos outage. However, as most customers will not experience any issues, we will not list these APIs as down. Desmos and Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 2 Ekim 2025 22:14 UTCmonitoring

   As of 22:12 UTC, Desmos services have been restored and Learnosity APIs are initializing without issue. Desmos and Learnosity Support and Systems Engineering teams will continue to monitor for a further 30 minutes before declaring this issue resolved. We will follow on with an update and resolution as soon as possible.

3. 2 Ekim 2025 22:43 UTCresolved

   As of 22:42 UTC, all Learnosity APIs are continuing to function as expected in all regions, and we are declaring this issue resolved. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

1. 19 Ağustos 2025 16:11 UTCinvestigating

   As of 3:40 UTC, we are experiencing degraded performance in our analytics stack affecting the availability of session data in US-East-1 for a subset of customers. This is affecting the Reports API and Data API. Neither authoring nor assessment stacks are affected, and there is no data loss. Submitted sessions are queueing for processing. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 19 Ağustos 2025 16:35 UTCinvestigating

   As of 4:30 UTC, we are continuing to investigate degraded performance in our Data and Reports APIs. Only availability of recently submitted session data is affected. Historic session data, as well as all other API stacks, remain unaffected. New submissions are persisting correctly with no data loss and these submission are being queued for scoring. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 19 Ağustos 2025 17:34 UTCidentified

   (Note: We're correcting cited UTC times to the 24 hr format and will include both forms in this update only.) As of 5:30pm/17:30 UTC, we've identified a possible contributing cause for the degraded performance in our analytics stack. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 19 Ağustos 2025 18:42 UTCidentified

   As of 18:30 UTC, initial remediation efforts have tripled the rate of queued session processing and we are continuing to work toward a full resolution. Access to recently submitted session results via the Data API and Reports API remains the only affected part of the Learnosity ecosystem. New submissions continue to be safely queued for scoring while the degraded performance remains. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

5. 19 Ağustos 2025 19:56 UTCidentified

   As of 19:30 UTC, we are now processing queued sessions rapidly and more than half of the backlog has already cleared.. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

6. 19 Ağustos 2025 20:35 UTCidentified

   As of 20:30 UTC, the scoring queue backlog is almost empty and new sessions will soon be processed without delay. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

7. 19 Ağustos 2025 21:05 UTCmonitoring

   As of 21:00 UTC, all sessions have been cleared from the scoring backlog queue and all submissions are being processed normally. Learnosity Support and Systems Engineering teams will monitor this situation for a further 30 minutes before calling it resolved.

8. 19 Ağustos 2025 21:31 UTCresolved

   As of 21:30 UTC, we are have resolved the issue affecting availability of session data in US-East-1. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

9. 19 Eylül 2025 19:14 UTCpostmortem

   ### Affected Systems and Regions On 19 August 2025, Learnosity experienced degraded performance in our analytics stack, affecting session data availability in US-East-1 for a subset of customers. This affected the Reports API and Data API, with no other stacks affected, and no data loss.  ### Investigation Monitoring detected a rapid increase in unprocessed and retried messages, along with elevated lock contention in the sessions database. The root cause was traced to a customer implementation issue generating an extraordinarily high number of submissions. This drove excessive retries, magnifying actual traffic volume.  The use of time-ordered v7 UUIDs for session IDs, normally handled without issue, became problematic under this contention. Uniqueness checks on each session ID required more resources and triggered a succession of temporary deadlocks. These deadlocks would usually self-resolve, but the amplified traffic prevented recovery, turning a minor issue into a sustained queue blockage. ### Resolution Once the issue was identified, Learnosity moved the customer to a dedicated, isolated sync queue, preventing cross‑tenant impact while we investigated. We applied targeted rate limits for the isolated service to protect the database, and drained the backlog. Where safe, long‑running queries were terminated to free locks and allow forward progress.  To support faster diagnosis, Learnosity enabled detailed deadlock logging and expanded metrics around message retries, abandonment, and per‑session activity. Learnosity also worked with the customer to adjust implementation settings, reducing combined saves and submits by two orders of magnitude. Session IDs were also switched to v4 UUIDs which simplified uniqueness checks further preventing deadlocks. Immediately after these changes were put into use, queues began to rapidly recover, and normal processing resumed. Most sessions for the subset of affected customers saw short delays, while the most significantly delayed session took ~6 hours before final persistence. Throughout, we identified no data loss. ### Prevention To prevent recurrence, we are: * Implementing targeted load tests and contention simulations to replicate high-parallelism patterns. * Reviewing customer identifier schemes for session IDs and auditing usage across all customers \(initial checks confirm none of our Top 50 customers currently use v7 UUIDs\). * Analyzing adoption of per-tenant fair-use queues \(or equivalent fair-share policies\) to cap burst throughput from a single tenant and protect shared infrastructure.

1. 8 Ağustos 2025 13:55 UTCinvestigating

   As of 13:40 UTC, we began investigating a possible issue affecting manual update jobs to session response scores, sessions statuses, and session metadata in the US-East-1 (VA) region. We saw a brief buildup in the queue for these jobs, the queue processed as expected, and is now empty. However, we're investigating further, out of an abundance of caution, to see if there are any unexpected causes for the short queue buildup. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 8 Ağustos 2025 13:57 UTCinvestigating

   As of 13:55 UTC, all manual update jobs have been executed and the jobs queue is empty. Requests to manually update session response scores, session statuses, and session metadata should execute as expected. We are still investigating possible reasons for the blip. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 8 Ağustos 2025 14:19 UTCresolved

   As of 14:10 UTC, we've found no negative behavior in the manual update processes and attribute the short burst of jobs to uncharacteristic testing of the new manual grading workflow. The jobs queue functioned as expected, ensuring no loss of requests, and the jobs were processed in a timely fashion. Learnosity will continue to monitor this activity for a further 60 minutes, but we are calling this resolved at this time. We apologize for the unwarranted alert. Please reach out if you have any questions or concerns.

4. 8 Ağustos 2025 14:19 UTCpostmortem

   At 13:40 UTC on 8 August 2025, we noticed a brief backup of asynchronous jobs affecting manual session updates in the US-East-1 \(VA\) region. Possible jobs including manual updates to response scores, session statuses, and session metadata. The queue mechanism worked as expected, and all requests were processed in short order. Out of an abundance of caution, we raised an alert while systems remained operational, but found nothing of concern during our investigation. We hope the unwarranted alert was not a significant distraction.

1. 3 Mart 2025 13:48 UTCinvestigating

   As of 13:45 UTC, we are experiencing delays in availability of session information in US-East-1 Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 3 Mart 2025 14:00 UTCinvestigating

   As of 14:00 UTC, we are still investigating an issue affecting the availability of session information in US-East-1. Both Data API and Reports API are experiencing extended delays and intermittent failures in returning session results. Authoring and Assessment APIs appear to be unaffected at this time and all session submissions are being successfully queued. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 3 Mart 2025 15:06 UTCinvestigating

   As of 15:00 UTC, we are continuing to investigate the issue. Data and Reports API are still impacted. Assessment and Authoring APIs remain unaffected. Assessment submissions are being queued and will be processed as the system works through any backlog queue. Note that if the Data API or Reports API is used in a preliminary/synchronous assessment delivery workflow, this will likely have a knock-on affect when initializing assessments. Initializing any assessment API directly is unaffected at present. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 3 Mart 2025 15:20 UTCmonitoring

   As of 15:15 UTC, all services have been restored. All queued messages have been processed and session information should now be available. Users of the Learnosity Firehose service will still see slight delays as messages are sent out for recently processed events. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

5. 3 Mart 2025 15:54 UTCresolved

   As of 15:45 UTC, after a further 30 minutes of monitoring, we are resolving this issue. All services remain fully operational. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalised any next steps or preventative measures required. Please reach out if you have any questions or concerns.

6. 14 Mart 2025 16:31 UTCpostmortem

   ### Affected Systems and Regions On March 3, 2025, we experienced a temporary service slowdown impacting the availability of session information in the US-East-1 region. The issue began at 13:19 UTC and was resolved by 15:15 UTC. The Data API and Reports API experienced delays and intermittent failures when returning session results. Authoring and Assessment APIs were unaffected with no data loss. ### Investigation We identified a recently introduced inefficient database query was causing unnecessary strain when handling extremely large data sets. This led to delayed responses to the Data API sessions endpoints. This further led to delays or unavailability in select reports via the Reports API. Additionally, some timeouts and safeguards that should have triggered earlier did not activate as expected. ### Resolution To quickly restore performance: * We optimized the affected queries, improving efficiency and reducing database load. * We scaled up the impacted systems to immediately process the backlog. * We fine-tuned system timeouts and connection limits to prevent similar issues in the future. Following these fixes, all services resumed normal operations. ### Prevention To prevent future occurrences: * We have permanently updated our database handling methods to ensure more efficient query execution. * We are enhancing automated monitoring to detect and respond to database slowdowns before they impact customers. We appreciate your patience and remain committed to delivering a seamless experience.

1. 9 Ocak 2025 13:33 UTCinvestigating

   As of 13:30 UTC, We are currently investigating a possible performance degradation affecting Reports API and Data API results in US-East-1. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 9 Ocak 2025 14:02 UTCinvestigating

   As of 14:00 UTC, Learnosity is working on identifying the cause of degraded performance in our Analytics APIs, Reports and Data. Authoring and Assessment stacks remain unaffected Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 9 Ocak 2025 14:13 UTCmonitoring

   As of 14:10 UTC, Learnosity has restored full service for all new requests to all Analytics APIs. We are monitoring stability and analyzing all queued requests. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

4. 9 Ocak 2025 14:50 UTCresolved

   As of 14:50 UTC, after a further 60 minutes of issue-free monitoring, we are resolving this issue affecting availability of session information via our Analytics stack. Reports API and Data API are fully operational. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalized any next steps or preventative measures required. Please reach out if you have any questions or concerns.

5. 14 Ocak 2025 17:25 UTCpostmortem

   **Affected Systems and Regions** On 2025-01-09, Learnosity experienced a brief partial outage affecting our analytics stacks, specifically the Reports API and Data API in the AMER region. The issue began at 13:30 UTC and was resolved at 14:06 UTC, lasting 36 minutes. All other API's were unaffected and there was no loss of data. **Investigation** We discovered that a large number of atypical, inefficient Data API queries requested by customers were taking too long to complete. This prevented other queries from running in a timely manner, creating a backlog. It was determined that an additional database index would significantly improve the response times of these types of queries. **Resolution** Immediately upon discovering this issue, the impacted database instances were successfully scaled up to ease the backlog of requests. The additional index was implemented and all remaining queries were processed quickly. Affected APIs returned to normal operations, and further monitoring ensured the issue was fully resolved. **Prevention** Following further testing, the new index is working well and has become a permanent part of the system. We are also adding new automated monitoring and regression testing to ensure similar requests perform as expected.

1. 1 Ekim 2024 15:09 UTCinvestigating

   As of 15:00 UTC, we are currently investigating an issue affecting the event delivery that powers the live progress report (live-activitystatus-by-user) in VA (us-east-1). Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 1 Ekim 2024 15:25 UTCidentified

   As of 15:20 UTC, the Systems Engineering team has identified the cause for the slower than normal delivery of events and is proceeding with mitigation steps. Learnosity Support and Systems Engineering teams are continuing to actively investigate the issue, and will follow on with an update and resolution as soon as possible.

3. 1 Ekim 2024 15:40 UTCmonitoring

   As of 15:35 UTC, the Systems Engineering team has deployed a fix, the errors have stopped, and currently all systems are functional. We will continue to monitor for a time before resolving the incident but we are currently seeing no errors. We will follow on with an update and resolution as soon as possible.

4. 1 Ekim 2024 16:07 UTCresolved

   As of 16:05 UTC, We are have resolved the issue affecting live progress reports in VA (us-east-1). As the recovery remains stable, we are now resolving the incident that was affecting live progress reports. Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalised any next steps or preventative measures required. Please reach out if you have any questions or concerns.

1. 13 Eylül 2024 14:35 UTCinvestigating

   As of 14:30 UTC, We are investigating a potential issue affecting the delivery of some Events API events (used in the live proctoring / live-activitystatus-by-user report) in us-east-1 (VA). Assessments are otherwise proceeding normally and can be saved and submitted without any issue. This issue if confirmed would only affect the delivery of Events API events. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 13 Eylül 2024 15:09 UTCidentified

   As of 15:00 UTC, the Learnosity Systems Engineering team has identified the issue preventing the assessment events from being delivered and are working on the implementation of remediation steps. Learnosity Support and Systems Engineering teams are continuing to work on the issue, and will follow on with an update and resolution as soon as possible.

3. 13 Eylül 2024 15:34 UTCmonitoring

   As of 15:30 UTC, events are flowing normally once again and all systems are operational. We will continue to monitor for some time before we resolve the issue fully to ensure we have a stable recovery.

4. 13 Eylül 2024 16:03 UTCresolved

   As of 16:00 UTC, after monitoring and confirming the stable state of the fixes put into place, we have resolved the Events API events delivery issue affecting proctored assessments in us-east-1 (VA). Learnosity Support and Systems Engineering teams will follow up with a post mortem once we have completed root cause analysis and finalised any next steps or preventative measures required. Please reach out if you have any questions or concerns.

1. 22 Mayıs 2024 18:27 UTCinvestigating

   As of 18:10 UTC, we are trying to determine if an issue exists causing a very small number of adaptive sessions to not trigger a Firehose event after scoring in US-East-1. This is just an internal investigation at present, without confirmation, and we have no evidence that any impact outside the described implementation is affected. Learnosity Support and Systems Engineering teams are actively investigating the issue, and will follow on with an update and resolution as soon as possible.

2. 22 Mayıs 2024 18:33 UTCinvestigating

   As of 18:30 UTC, Learnosity Support and Systems Engineering teams are continuing to investigate this unconfirmed issue and will follow on with an update as soon as possible.

3. 22 Mayıs 2024 18:47 UTCinvestigating

   As of 18:45 UTC, Learnosity Support and Systems Engineering teams are continuing to investigate an unconfirmed issue, examining less than 500 potentially affected sessions out of 4.93 million submitted over the same period. We will follow on with an update as soon as possible.

4. 22 Mayıs 2024 19:01 UTCmonitoring

   As of 19:00 UTC, we have been unable to find any systemic problems, while the number of potentially impacted sessions remains at one hundredth of one percent ( 0.01%) of total submissions over the period investigated, likely due to a content issue. Learnosity Support and Systems Engineering teams will continue to monitor for 30 minutes and expect to close this investigation at that time.

5. 22 Mayıs 2024 19:42 UTCresolved

   As of 19:40 UTC, we believe we've identified content to be the root cause of this tiny number of sessions not passing through scoring and triggering a Firehose event. We've reached out to customer proactively and will help address this issue directly. We are now calling this issue resolved and apologize for any distractions. Please reach out if you have any questions or concerns.