Is Discover down? User reports show no current problems with Discover

Is Discover down right now?

For most users, sign in works and the account opens. When discover down reports jump, it is a login story almost every time: in one reported outage, about three quarters of all problems were people who could not log in at all, split between the website and the app. This page tracks the live discover status from reports near you, so a wide discover outage stands apart from a fault on your own device.

The signature failure is a polite dead end: your request cannot be completed at this time. Users have met it for hours, on computer and phone at once.

Is Discover down for me or everyone?

When the website and the app fail together with the same message, treat it as everyone until reports here calm down: users describe the pair failing for hours, then clearing together. When one door works, use it, and keep retries on one device so the lock counter stays low.

The request cannot be completed loop

That message is the service refusing the session mid flow, not a comment on your password. It loops: sign in, apology, sign in, apology. Because it looks like a detail is wrong, people keep retrying, and the retries stack into the second fault, the lock.

It also strikes mid task: customers have been kicked out while adding a card to a phone wallet, then locked into the loop at sign in.

Locked out after failed attempts

Failed attempts stack into a timed lock, and the account then refuses even the right password. Locks clear in about a quarter of an hour, but only while attempts stop. Then one careful sign in, typed by hand. Locks clear when the tries stop here, while Divvy admins watch spend caps block company cards in silence there.

When your browser is the fault

One browser case is on record: an update quietly broke discover.com sign in for that browser alone, while an older version and the app kept working. Sites trust only certain browser builds, and a new one can fall off the list. If the app opens your account, the browser is the fault.

Codes to old numbers, and maintenance

A new device or place triggers a verification code, stranding anyone whose phone number on file is old. Maintenance takes the same door offline in short planned windows.

Common Discover Problems and Fixes

Login faults lead the reports. Start with yours.

Request cannot be completed error loop

That message is the site refusing the session, not your password. Stop retrying: stacked attempts can lock the account. Check this page; if reports are climbing, the loop is theirs and waiting is the fix. If calm, clear the site data or switch to the app.

Locked out after failed attempts

Locks clear with time, often around a quarter of an hour, but only if the attempts stop. Wait it out, then sign in once with the password typed by hand.

Can not log in on the website or the app

When both fail together with the same message, treat it as an outage until this page calms down: users report the pair failing for hours, then clearing together.

Sign in broke after a browser update

Sites can quietly stop trusting a brand new browser build. Test the app and a second browser: if either opens your account, the account is fine and the first browser is the fault.

Verification code for a new device never lands

Codes go to the phone or email on file. If that number changed, the code is going to the old one. One successful sign in on a known device lets you update the number.

Having a problem with Discover?

Comments are public and help others understand the issue.

Subscribe

Login

Notify of

new follow-up comments new replies to my comments

Label

{} [+]

Name*

Email*

Label

{} [+]

Name*

Email*

0 Comments

Oldest

Newest Most Voted