- Detected by Pingoru
- May 05, 2026, 08:36 PM UTC
- Resolved
- May 07, 2026, 06:36 PM UTC
- Duration
- 1d 21h
Affected: Plaid
Timeline · 2 updates
-
identified May 05, 2026, 08:36 PM UTC
We've identified a widespread issue with TD Canada where connections are failing or, if successful, transactions are not importing. Our Direct Import provider is aware of and working on this! Please continue to use our other transaction entry methods to keep your accounts up to date.
-
resolved May 07, 2026, 06:36 PM UTC
Our import provider has confirmed this issue with TD Canada has been resolved. If you're still running into issues, please try to refresh the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Apr 14, 2026, 02:36 PM UTC
- Resolved
- Apr 14, 2026, 02:41 PM UTC
- Duration
- 4m
Affected: Website (www.ynab.com)
Timeline · 2 updates
-
investigating Apr 14, 2026, 02:36 PM UTC
Our partner, Kustomer, is down. We are waiting on a status update.
-
resolved Apr 14, 2026, 02:41 PM UTC
This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 12, 2026, 03:03 PM UTC
- Resolved
- Mar 12, 2026, 06:12 PM UTC
- Duration
- 3h 8m
Affected: Mobile Apps (iOS and Android)
Timeline · 3 updates
-
investigating Mar 12, 2026, 03:03 PM UTC
YNAB is currently experiencing reports of established users entering onboarding. To override this, try uninstalling and reinstalling the YNAB mobile app. We're investigating and will update here as soon as we know more.
-
monitoring Mar 12, 2026, 04:33 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Mar 12, 2026, 06:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Mar 06, 2026, 07:20 AM UTC
- Resolved
- Mar 06, 2026, 07:47 AM UTC
- Duration
- 26m
Affected: Web App (app.ynab.com)
Timeline · 2 updates
-
investigating Mar 06, 2026, 07:20 AM UTC
The web app won't load for a contingent of customers. We are currently investigating this issue. Mobile users can use the app offline but it won't be able to sync, access settings, or the account widget.
-
resolved Mar 06, 2026, 07:47 AM UTC
This incident has been resolved!
Read the full incident report →
- Detected by Pingoru
- Mar 02, 2026, 10:17 PM UTC
- Resolved
- Mar 04, 2026, 08:13 PM UTC
- Duration
- 1d 21h
Affected: Web App (app.ynab.com)
Timeline · 3 updates
-
investigating Mar 02, 2026, 10:17 PM UTC
We are experiencing an issue with the onboarding flow reappearing in existing plans on the web app. This is blocking some settings, as well as causing an "Under Construction" error to appear for customers who share plans through YNAB Together. We have identified the source of the issue, and are working to release a fix. In the meantime, clicking through the prompts in the onboarding flow will clear it from your plan.
-
monitoring Mar 02, 2026, 11:48 PM UTC
We changed how onboarding progress is stored, and that caused onboarding to reset for some users. If you encounter sudden limitations, your best course is to go through those onboarding steps, being sure to select Fund Categories in the savings popup. We've released a fix that should keep any new customers from experiencing the onboarding flow being re-deployed, but feel free to reach out to Support at [email protected] if you run into any further issues.
-
resolved Mar 04, 2026, 08:13 PM UTC
After a release Monday Mar 2, 2026, many budgets were put back into an onboarding state. We ran several cleanup scripts which marked those budgets as having completed onboarding to resolve the issue. Some users who logged in before we ran those scripts saw the onboarding dialogs even though they’d been active users for years, and some users were unable to access budgets shared via YNAB Together. This issue has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 20, 2026, 03:00 AM UTC
- Resolved
- Jan 20, 2026, 03:17 AM UTC
- Duration
- 16m
Timeline · 3 updates
-
investigating Jan 20, 2026, 03:00 AM UTC
We will be having a brief planned maintenance at 10PM Eastern.
-
identified Jan 20, 2026, 03:01 AM UTC
We will be having a brief planned maintenance at 10PM Eastern.
-
resolved Jan 20, 2026, 03:17 AM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 04:13 PM UTC
- Resolved
- Jan 15, 2026, 11:49 PM UTC
- Duration
- 7h 36m
Affected: Mobile Apps (iOS and Android)
Timeline · 3 updates
-
investigating Jan 15, 2026, 04:13 PM UTC
We are getting reports of the iOS app crashing. We're investigating and will update here as soon as we know more.
-
identified Jan 15, 2026, 06:17 PM UTC
We have found the crash only affects iOS 18.0 through 18.3.x. We are working on a hotfix for the issue or you can upgrade to a higher version of iOS.
-
resolved Jan 15, 2026, 11:49 PM UTC
Our developers found the problem and have successfully deployed a hotfix. Feel free to head back to YNAB and test things out!
Read the full incident report →
- Detected by Pingoru
- Jan 15, 2026, 12:05 AM UTC
- Resolved
- Feb 02, 2026, 11:01 PM UTC
- Duration
- 18d 22h
Affected: PlaidMX
Timeline · 3 updates
-
identified Dec 12, 2025, 12:05 AM UTC
Our import provider is aware of an issue impacting CIBC connections. Continue to use our other transaction entry methods to keep your accounts up to date!
-
identified Feb 02, 2026, 11:01 PM UTC
Unfortunately, this issue with CIBC is proving to be much more complex to resolve than was originally anticipated and is now considered a long-term issue. While work will continue to be done behind the scenes, we'll be retiring this from our Status Page to keep the information here as fresh and relevant as possible. In the meantime, we recommend trying to connect every few weeks just in case our providers fix it before we're notified!
-
resolved Feb 02, 2026, 11:01 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 18, 2025, 12:14 PM UTC
- Resolved
- Nov 18, 2025, 03:12 PM UTC
- Duration
- 2h 58m
Affected: Mobile Apps (iOS and Android)Web App (app.ynab.com)Website (www.ynab.com)Public API
Timeline · 3 updates
-
investigating Nov 18, 2025, 12:14 PM UTC
Due to an issue with one of our upstream providers, app.ynab.com, www.ynab.com, and other websites may load intermittently. We'll update here as we have more information.
-
identified Nov 18, 2025, 12:32 PM UTC
Our upstream provider has identified the issue and is working to resolve it.
-
resolved Nov 18, 2025, 03:12 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Nov 04, 2025, 09:58 PM UTC
- Resolved
- Nov 06, 2025, 06:48 PM UTC
- Duration
- 1d 20h
Affected: PlaidMX
Timeline · 2 updates
-
identified Nov 04, 2025, 09:58 PM UTC
YNABers are reporting seeing a "403 Forbidden Error" when trying to connect. Our import provider is aware of the issue and has confirmed Navy Federal Credit Union is currently experiencing some downtime. Please continue to use our other transaction entry methods to keep your accounts up to date!
-
resolved Nov 06, 2025, 06:48 PM UTC
After monitoring Navy Federal Credit Union’s connection for the past few days, we’ve confirmed it's resolved. If you're still running into issues, please try to refresh the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Oct 30, 2025, 06:15 PM UTC
- Resolved
- Jan 14, 2026, 09:09 PM UTC
- Duration
- 76d 2h
Affected: MX
Timeline · 4 updates
-
identified Oct 30, 2025, 06:15 PM UTC
Our import provider is aware of an issue impacting Fidelity connections. They've identified the issue’s cause and are working with Fidelity. You can continue to use our other transaction entry methods to keep your accounts up to date. ⚠️Investment account holders (including Cash Management account): Please note that we expect these to have issues connecting or import incorrectly. See "I'm having trouble with my investment or loan account" for further information.
-
identified Nov 06, 2025, 07:23 PM UTC
Issues persist while our import provider continues to work on a resolution, but we are seeing *some* improvement in connection stats. We suggest refreshing the bank connection occasionally, as this may help you get reconnected before the incident is officially resolved!
-
resolved Jan 14, 2026, 09:09 PM UTC
Unfortunately, this issue with Fidelity Investments is proving to be more complex to resolve than anticipated. It is now considered a long-term issue. While work will continue to be done behind the scenes to restore the connection, we'll be retiring this from our Status Page to keep the information here as fresh and relevant as possible. We'll post a final update here once it's resolved. In the meantime, we recommend trying to connect every few weeks just in case our providers release a fix before we're notified.
-
postmortem May 12, 2026, 09:21 PM UTC
We have some good news to share! Our import provider has upgraded Fidelity to a direct, OAuth connection, so we are now resolving the long-standing incident. Please keep in mind we still can’t troubleshoot connection or data quality issues with **investment-based** accounts, like Cash Management accounts \(CMAs\). You can find more info on that [here](https://support.ynab.com/en_us/im-having-trouble-with-my-investment-or-loan-account-SJAyeIpwll). If you have any other questions, please feel free to reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Oct 27, 2025, 09:54 PM UTC
- Resolved
- Oct 27, 2025, 10:57 PM UTC
- Duration
- 1h 3m
Affected: Web App (app.ynab.com)
Timeline · 3 updates
-
investigating Oct 27, 2025, 09:54 PM UTC
Some YNABers are unable to load YNAB on web. We're investigating the issue now.
-
monitoring Oct 27, 2025, 10:50 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Oct 27, 2025, 10:57 PM UTC
We did it! This incident is resolved.
Read the full incident report →
- Detected by Pingoru
- Oct 20, 2025, 07:55 PM UTC
- Resolved
- Oct 20, 2025, 11:02 PM UTC
- Duration
- 3h 7m
Timeline · 3 updates
-
identified Oct 20, 2025, 07:55 PM UTC
The software we use for our support responses has been affected by the AWS outage today. If you've already reached out to support, you may experience a delay in us getting back to you. If you need to contact support, please send an email directly to [email protected] .
-
monitoring Oct 20, 2025, 08:42 PM UTC
Our support software is working on a fix and we're preparing to resume support responses.
-
resolved Oct 20, 2025, 11:02 PM UTC
Our Support software is back up and running and so is our team 🎉
Read the full incident report →
- Detected by Pingoru
- Sep 25, 2025, 07:39 PM UTC
- Resolved
- Sep 25, 2025, 09:51 PM UTC
- Duration
- 2h 11m
Affected: Web App (app.ynab.com)
Timeline · 3 updates
-
investigating Sep 25, 2025, 07:39 PM UTC
We've received several reports of degraded web app performance. We're investigating the issue.
-
monitoring Sep 25, 2025, 09:12 PM UTC
A fix has been implemented and we are monitoring the results.
-
resolved Sep 25, 2025, 09:51 PM UTC
This incident has been resolved.
Read the full incident report →
Critical September 3, 2025 - Detected by Pingoru
- Sep 03, 2025, 08:22 AM UTC
- Resolved
- Sep 03, 2025, 08:41 AM UTC
- Duration
- 19m
Affected: Web App (app.ynab.com)
Timeline · 3 updates
-
investigating Sep 03, 2025, 08:22 AM UTC
YNAB is currently experiencing an outage. We're investigating and will update here as soon as we know more.
-
investigating Sep 03, 2025, 08:40 AM UTC
We are continuing to investigate this issue.
-
resolved Sep 03, 2025, 08:41 AM UTC
Our developers found the problem and have successfully deployed the release. Feel free to head back to your budget and test things out!
Read the full incident report →
- Detected by Pingoru
- Aug 27, 2025, 02:15 PM UTC
- Resolved
- Aug 27, 2025, 08:24 PM UTC
- Duration
- 6h 9m
Affected: Mobile Apps (iOS and Android)Web App (app.ynab.com)
Timeline · 2 updates
-
identified Aug 27, 2025, 02:15 PM UTC
The web app and mobile syncing are seeing slower response times as we do some database maintenance.
-
resolved Aug 27, 2025, 08:24 PM UTC
Database maintenance is complete. Loading and syncing times are back to normal.
Read the full incident report →
- Detected by Pingoru
- Aug 13, 2025, 05:29 PM UTC
- Resolved
- Aug 13, 2025, 06:31 PM UTC
- Duration
- 1h 1m
Affected: Web App (app.ynab.com)
Timeline · 2 updates
-
investigating Aug 13, 2025, 05:29 PM UTC
We are currently investigating this issue.
-
resolved Aug 13, 2025, 06:31 PM UTC
This incident has been resolved.
Read the full incident report →
- Detected by Pingoru
- Jun 12, 2025, 09:06 PM UTC
- Resolved
- Jun 26, 2025, 07:43 PM UTC
- Duration
- 13d 22h
Affected: PlaidMX
Timeline · 2 updates
-
investigating Jun 05, 2025, 09:06 PM UTC
We're investigating a spike in duplicate transaction issues with Chase *credit card* accounts. Duplicate transactions are typically a one-time occurrence, so we ask that you please refer to our Troubleshooting Linked Accounts article for next steps! If duplicates continue to import after you've followed those steps, you can reach out to us at [email protected] with: (1) your credit card account name and (2) a screenshot how those transactions look in YNAB. Then we'll be able to troubleshoot the issue further with our import providers.
-
resolved Jun 26, 2025, 07:43 PM UTC
After monitoring this issue over the past month, we have confirmed it's resolved. If you've already tried removing and re-adding your Chase connection and duplicates have imported since, please reach out to us with the Chase credit card account name and transaction examples at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Jun 11, 2025, 02:57 PM UTC
- Resolved
- Jun 19, 2025, 08:37 PM UTC
- Duration
- 8d 5h
Affected: PlaidMX
Timeline · 4 updates
-
investigating Jun 11, 2025, 02:57 PM UTC
We're investigating a spike in connection issues and transactions not importing for Scotiabank. We're working with our Direct Import provider to learn more, and we'll post updates here as we have them. In the meantime, use our other transaction entry methods to keep your accounts up to date!
-
identified Jun 12, 2025, 04:25 PM UTC
We've identified the issue’s cause and are working with our Direct Import provider on the next steps. We'll continue to keep you updated as things progress! Continue to use our other transaction entry methods to keep your accounts up to date.
-
monitoring Jun 16, 2025, 04:28 PM UTC
Our Direct Import provider has resolved the issue with Scotiabank. Please remove and re-add the connection if you're still running into issues. We’ll continue to monitor the situation for the next few days, so if you need more help after removing and re-adding the connection, write to [email protected]!
-
resolved Jun 19, 2025, 08:37 PM UTC
After monitoring Scotiabank’s connection for the past few days, we’ve confirmed it's resolved. If you're still running into issues, please try to remove and re-add the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- May 06, 2025, 01:00 AM UTC
- Resolved
- Jun 05, 2025, 04:47 PM UTC
- Duration
- 30d 15h
Affected: Plaid
Timeline · 7 updates
Read the full incident report →
- Detected by Pingoru
- May 06, 2025, 12:23 AM UTC
- Resolved
- May 06, 2025, 06:27 PM UTC
- Duration
- 18h 4m
Affected: Mobile Apps (iOS and Android)
Timeline · 3 updates
-
investigating May 06, 2025, 12:23 AM UTC
We are hearing reports of slowness or unresponsiveness on the iOS app. We are currently investigating this issue!
-
investigating May 06, 2025, 03:02 PM UTC
We are continuing to investigate this issue.
-
resolved May 06, 2025, 06:27 PM UTC
This incident has been resolved! If you're still seeing issues, please delete and reinstall your mobile app to get the latest version!
Read the full incident report →
- Detected by Pingoru
- Apr 10, 2025, 07:08 PM UTC
- Resolved
- May 06, 2025, 08:45 PM UTC
- Duration
- 26d 1h
Affected: PlaidMX
Timeline · 5 updates
-
investigating Mar 25, 2025, 06:39 PM UTC
We're investigating a spike in connection issues with Tangerine Bank (CA). We're working with our Direct Import provider to learn more, and we'll post updates here as we have them. In the meantime, use our other transaction entry methods to keep your accounts up to date!
-
identified Mar 27, 2025, 07:08 PM UTC
We've identified the issue’s cause and are working with our Direct Import provider on the next steps. We'll continue to keep you updated as things progress. In the meantime, we noticed Tangerine's page suggests logging in with either your Client Number, Card Number, or Username and a few users have had luck getting reconnected when using one versus the other (i.e., logging in with their card number instead of their client number). Though this is unexpected, it may be worth trying in case it gets you reconnected more quickly! Otherwise, please continue to use our other transaction entry methods to keep your accounts up to date.
-
identified Apr 17, 2025, 09:09 PM UTC
Our import provider is continuing to work on this issue, but there are no actionable updates to share at this time. Thank you for hanging in there with us!
-
monitoring Apr 29, 2025, 08:04 PM UTC
Our Direct Import provider has resolved the issue with Tangerine. Follow the prompts to reauthorize the connection, or remove and re-add the connection if you're still running into issues. We’ll continue to monitor the situation for the next few days, but if you need more help, write to [email protected]!
-
resolved May 06, 2025, 08:45 PM UTC
After monitoring Tangerine’s connection for the past week, we’ve confirmed it's resolved. If you're still running into issues, please try to remove and re-add the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Apr 03, 2025, 04:16 PM UTC
- Resolved
- Apr 10, 2025, 09:53 PM UTC
- Duration
- 7d 5h
Affected: PlaidMX
Timeline · 3 updates
-
investigating Apr 03, 2025, 04:16 PM UTC
We're investigating a spike in $0.00 transaction imports from Charles Schwab. These incorrect transactions will no longer import while we work with our Direct Import provider to learn more. We'll post updates here as we have them. In the meantime, you can delete the $0.00 transactions. If your issue doesn’t match this description or you're missing real transactions, remove and re-add the connection. If the issue persists, write to [email protected]!
-
monitoring Apr 08, 2025, 07:47 PM UTC
Charles Schwab has fixed the bug that was causing $0.00 transactions. You will need to delete any transactions that imported incorrectly before today, and you should no longer see this issue moving forward. Follow the prompts to reauthorize the connection, or remove and re-add the connection if you're still running into issues. We’ll continue to monitor the situation for the next few days, but if you need more help, write to [email protected]!
-
resolved Apr 10, 2025, 09:53 PM UTC
After monitoring Charles Schwab for the past few days, we’ve confirmed this issue is resolved. If you're still running into issues, please try to remove and re-add the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Mar 27, 2025, 07:30 PM UTC
- Resolved
- Apr 03, 2025, 07:01 PM UTC
- Duration
- 6d 23h
Affected: PlaidMX
Timeline · 3 updates
-
investigating Mar 27, 2025, 07:30 PM UTC
We're investigating a spike in transactions not importing for Target Credit Card. We're working with our Direct Import provider to learn more, and we'll post updates here as we have them. In the meantime, use our other transaction entry methods to keep your accounts up to date! If your issue doesn’t match this description, please check to see if it's a known issue on our Watchlist Institutions article so you can monitor the status of your bank there.
-
monitoring Apr 01, 2025, 05:38 PM UTC
Our Direct Import provider has resolved the issue with Target Credit Card. Follow the prompts to reauthorize the connection, or remove and re-add the connection if you're still running into issues. We’ll continue to monitor the situation for the next few days, but if you need more help, write to [email protected]!
-
resolved Apr 03, 2025, 07:01 PM UTC
After monitoring Target Credit Card’s connection, we’ve confirmed it's resolved. If you're still running into issues, please try to remove and re-add the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →
- Detected by Pingoru
- Feb 27, 2025, 10:09 PM UTC
- Resolved
- Mar 11, 2025, 03:41 PM UTC
- Duration
- 11d 17h
Affected: Plaid
Timeline · 5 updates
-
investigating Jan 24, 2025, 02:05 AM UTC
We're investigating a spike in reports of missing CC accounts for Desjardins. We're working with our Direct Import provider to learn more, and we'll post updates here as we have them. In the meantime, you might be able to link your credit card via the "Desjardins VISA" option in the list or use our other transaction entry methods to keep your accounts up to date! If your issue doesn’t match this description, please check to see if it's a known issue on our Watchlist Institutions article so you can monitor the status of your bank there.
-
identified Jan 30, 2025, 09:53 PM UTC
We've identified the cause of the issue and are working with our Direct Import provider on the next steps. We'll continue to keep you updated as things progress! Again, you may be able to link your credit card via the "Desjardins VISA" option in the list. Otherwise, please continue to use our other transaction entry methods to keep your credit card accounts up to date.
-
investigating Jan 30, 2025, 10:09 PM UTC
While I don't have anything actionable to update you on, we have heard from Plaid who has escalated this issue with their engineering team. We'll continue to give updates as we have them in the meantime. Keep on keeping on!
-
monitoring Mar 06, 2025, 08:46 PM UTC
Our Direct Import provider has resolved the issue with Desjardins. 🥳 If you're still not seeing a credit card account listed, remove and re-add the Desjardins connection to see if it appears and re-link all accounts to the new connection. We’ll continue to monitor the situation for the next few days, but if you need more help, write to [email protected]!
-
resolved Mar 11, 2025, 03:41 PM UTC
After monitoring Desjardins for the past few days, we’ve confirmed it's resolved. If you're still running into issues, please try to remove and re-add the connection, and if the issue persists, reach out to us at [email protected]!
Read the full incident report →