Investigating - Investigating:
Users using Android mobile devices or tablets may encounter Push notification failures.
User Impact:
Users using Android mobile devices or tablets may be unable to log on using Push2Accept or Symbol2Accept due to push notification failures. The issue may manifest itself in a number of ways:
1. In some cases, the push notification may not be received
2. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, no error will be displayed on the mobile device
3. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, an error may be displayed on the mobile device
Preliminary RCA:
This issue is caused by the Android OS app update process. For some devices, when the app is updated, the unique identifier used to validate the device to our cloud is modified by the Android OS, resulting in push notifications failing. The SecureAuth development team is currently investigating this issue with the Google Android team.
Remediation:
Users must reenroll the impacted devices
Nov 16, 18:52 UTC
Users using Android mobile devices or tablets may encounter Push notification failures.
User Impact:
Users using Android mobile devices or tablets may be unable to log on using Push2Accept or Symbol2Accept due to push notification failures. The issue may manifest itself in a number of ways:
1. In some cases, the push notification may not be received
2. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, no error will be displayed on the mobile device
3. In some cases, pressing “accept” or pressing the symbol, the user will not be logged in, an error may be displayed on the mobile device
Preliminary RCA:
This issue is caused by the Android OS app update process. For some devices, when the app is updated, the unique identifier used to validate the device to our cloud is modified by the Android OS, resulting in push notifications failing. The SecureAuth development team is currently investigating this issue with the Google Android team.
Remediation:
Users must reenroll the impacted devices
Nov 16, 18:52 UTC
SecureAuth Titan Services
Operational
Dashboard Service
Operational
Device Enrollment Service
Operational
Fraud Service
Operational
IP Blocking Service
Operational
IP Intel Service
Operational
IP Reporting Service
Operational
Licensing Service
Operational
Link-to-Accept Service
Operational
OAuth Service
Operational
Push-to-Accept Service
Operational
SMS Service
Operational
Symbol-to-Accept Service
Operational
Telephony Service
Operational
User Risk Service
Operational
User Risk Scoring Service
Operational
User Stats Service
Operational
Transaction Service
?
Operational
SecureAuth Cloud Services
Operational
3rd Party Mobile Carrier
Operational
Enhanced Geolocation Resolution Service - US1
Operational
Enhanced Geolocation Resolution Service - US2
Operational
Fraud Service - US1
Operational
Fraud Service - US2
Operational
Geolocation Resolution Service - US1
Operational
Geolocation Resolution Service - US2
Operational
Nexmo Voice API
Operational
Push-to-Accept Service - US1
?
Operational
Push-to-Accept Service - US2
?
Operational
SMS Service - US1
Operational
SMS Service - US2
Operational
Telephony Extension/DTMF Service - US1
Operational
Telephony Extension/DTMF Service - US2
Operational
Telephony Provider SMS API
Operational
Telephony Service - US1
Operational
Telephony Service - US2
Operational
Threat Service - US1
Operational
Threat Service - US2
Operational
X.509 Certificate Service (SHA2) - US1
Operational
X.509 Certificate Service (SHA2) - US2
Operational
SecureAuth IdP Frontend Services
Operational
SecureAuth Web Admin
Operational
SecureAuth Application Templates
Operational
GitHub Git Operations
Operational
Operational
Degraded Performance
Partial Outage
Major Outage
Maintenance
Major outage
Partial outage
No downtime recorded on this day.
No data exists for this day.
had a major outage.
had a partial outage.
Scheduled Maintenance
US2 DNS Cutover to AWS
Dec 9, 19:00-20:00 UTC
SecureAuth will be routing all traffic currently to US2 to services in AWS data centers. Please ensure the proper IPs are whitelisted or service will be disrupted. Follow the documentation linked below for more details. https://docs.secureauth.com/2104/en/secureauth-cloud-services.html#allowed-urls-and-ip-addresses-for-secureauth-cloud-services
Posted on Dec 1, 19:20 UTC
Posted on Dec 1, 19:20 UTC