Web app not working — anyone else having issues?
malgorzatakrupaa says:
Hi,
is anyone else having trouble with the Remember The Milk web app today? Whenever I try to open it, the page fails to load and shows a message suggesting to try again or check the troubleshooting steps.
I’ve already tried refreshing, and using different browsers and devices, but nothing seems to work.
Is this a general outage or something on my side?
Thanks in advance for any help!
is anyone else having trouble with the Remember The Milk web app today? Whenever I try to open it, the page fails to load and shows a message suggesting to try again or check the troubleshooting steps.
I’ve already tried refreshing, and using different browsers and devices, but nothing seems to work.
Is this a general outage or something on my side?
Thanks in advance for any help!
bdavison says:
It's also affecting the Windows desktop app, and access via browsers. I used their contact form to inquire at 3:45 EST. My Android phone app is still functional, but most likely operating in offline mode.
Just had similar problem. First appeared while trying to export/backup. Then I upgraded firefox (it was nagging). Then could not load the login page. Clearing cookies and site data for rememberthemilk brought me to the login page once. Then after that will not load (and nothing to clear).
bdavison says:
I'm not sure whether that's recent. I think I've seen "under maintenance" in the past whenever any of the components below it have the wrench symbol. I never found the status page to be very useful during outages.
The white on blue sub "Service Under Maintenance" header is always there. It means the integration with apps/platforms like X/Twitter and Google Assistant are not working. They need maintenance on the RTM side to keep up with changes in the other platforms. So it's not a reliable indicator of anything atm.
The first post in this thread was 4:25 pm Eastern, about 8 hours ago. I saw the problem at 8:30pm eastern about 4 hours ago. No change now at 12:45am 11/01/2025(early am). Still can't load page. Status page does not report the problem. No one responded to my ticket, and I didn't get an automated response.
Same here (Germany). Not working on Chrome and Edge on Win 11 and Chrome on ChromeOS flex for more than 12 hours now. Nothing on https://status.rememberthemilk.com/ - so far no answer to my support request. Android app works, but is not helpful for me because I use a lot of links I need on my desktop PC.
dyehardz says:
same here.
tm124c41 says:
Same here in Japan. Web version hasn’t worked.
renz3 says:
@arendvr.com: ThankU!
malgorzatakrupaa says:
Thank you!
Thank you all for reporting. I was starting to think it was just me. That old web app loads but won't do it for me, I've gone too far in on "new" features.
I see a similar thread from last July but I cannot tell how long it took them to fix it then.
https://www.rememberthemilk.com/forums/help/31471/
I see a similar thread from last July but I cannot tell how long it took them to fix it then.
https://www.rememberthemilk.com/forums/help/31471/
How can you switch to the old app if you can't login?
(I always get an error before the progress bar reaches 25%)
Things like this can happen, but the way the RTM team does (not) handle this (timely) makes me really wonder whether I should finally migrate to another service after all those years :(
(I always get an error before the progress bar reaches 25%)
Things like this can happen, but the way the RTM team does (not) handle this (timely) makes me really wonder whether I should finally migrate to another service after all those years :(
momoy says:
Same here! Help me~
nilaco says:
Same problem here.
Most unacceptable is the lack of even an acknowledgement. For all we know, they may not be aware yet that there's a problem.
The browser console error is "net::ERR_HTTP2_PROTOCOL_ERROR 200", however note a different network error is given with HTTP2 disabled. Save you trying that like I did.
The browser console error is "net::ERR_HTTP2_PROTOCOL_ERROR 200", however note a different network error is given with HTTP2 disabled. Save you trying that like I did.
Same issue here. Submitted a support request. Status page still shows no reported incidents. This started for me yesterday but was spotty. Today, the web app is completely non-functional, won't even load halfway and I also can confirm that the error in the web console is showing "Failed to load resource: net::ERR_HTTP2_PROTOCOL_ERROR"
This is horrible communication and terrible customer service from a company I've been paying for years to provide a service that many other competitors could also provide. Shameful.
This is horrible communication and terrible customer service from a company I've been paying for years to provide a service that many other competitors could also provide. Shameful.
ashineko says:
Another one in the same boat. I'm glad I started keeping a bullet journal last year, but there are still some repeated tasks that are easier to manage via RTM.
Working now for me! :D :D
First report of broken: 4:25pm EDT 10/31/2025
First report of working: 11:19am EDT 11/01/2025
Total duration of outage: 18hr 54min.
That's long for an internet service in 2025 but it's <24 hrs fortunately.
And no one has yet mentioned: the service went out on Halloween. It was clearly some malevolent force :)
First report of broken: 4:25pm EDT 10/31/2025
First report of working: 11:19am EDT 11/01/2025
Total duration of outage: 18hr 54min.
That's long for an internet service in 2025 but it's <24 hrs fortunately.
And no one has yet mentioned: the service went out on Halloween. It was clearly some malevolent force :)
steve23606 says:
Shocking service. Unprofessional. I left RTM last year and glad I did. The original creators have abandoned the project but happy to take the money. This incident confirms what many have suggested - that RTM is abandonware.
I understand the sentiment and it is justified. However if it truly was *abandon*ware, it would not have come back up. Someone on the staff noticed (eventually) and fixed it. So, by definition, someone paid attention and took action (and I am VERY appreciative they did) and so it's not "abandoned". It does appear to be de-prioritized, unfortunately. And maintenance is slow. Those criticisms are still warranted.
steve23606 says:
@nah.why Lots of baseless assumption there. The outage may have been down to a third party. Regardless, no-one at RTM communicated publicly. Therefore = abandonware.
My Pro is up for renewal in December. I hope (but don’t expect) that we get an apology and post-mortem soon. If not, I should (reluctantly) consider migrating to a different service. RTM works great for me, when it works, but I “need”/want a confirmation that I can still trust it.
I agree. The real issue here is not (only) the outage, but the missing communication. I don't want to move to another service, but I do need a reliable app and support. I didn't get a response to my support request, no reaction here in the forum, and no incident report on the status page. That is not good. My subscription period has more than 100 days left, and then I will decide if I resubscribe. And do regular backups until then.
steve23606 says:
@sara.call I went to Todoist. I had about 300 outstanding tasks and moved them all manually over a period of a couple of weeks.
emily (Remember The Milk) says:
Hi all, I’m really sorry it took us longer than usual to respond here. 😞
We wanted to share what happened with some downtime we experienced over the weekend, beginning the evening of October 31 and continuing into the morning of November 1. We're really sorry to those of you who were affected by this outage.
What happened?
A subset of users were routed to a web server that was failing intermittently (it kept dropping out of the server pool, then recovering briefly, then failing again -- also known as "flapping").
We have multiple monitoring systems, but because the server was going in and out, they didn't catch the full scope of the issue. This led to a delayed response from our team. Once we diagnosed and fixed the affected server, everything returned to normal.
Our communication
We're normally quick to update everyone when something goes wrong, but this time we let you down. A combination of the delay in detecting the issue, and the timing on Halloween night, meant that we didn't provide updates as we usually would. We're really sorry for the silence -- we know that made the outage more frustrating.
What we're doing now
We're making a few changes to try and avoid an issue of this kind reoccurring in the future, including extra monitoring and alerting, more redundancy in our notifications, and better detection of sudden increases in support volume that might indicate an undetected problem. We'll also make sure we communicate sooner if anything like this happens again.
Thank you
Thanks so much for your patience, and to everyone who reached out to let us know that something wasn't right. We're working to make sure that RTM stays reliable, and that we're communicative when we encounter issues like this.
If you’re still seeing any issues, please let us know. 💙
(Also posted over on the status site.)
We wanted to share what happened with some downtime we experienced over the weekend, beginning the evening of October 31 and continuing into the morning of November 1. We're really sorry to those of you who were affected by this outage.
What happened?
A subset of users were routed to a web server that was failing intermittently (it kept dropping out of the server pool, then recovering briefly, then failing again -- also known as "flapping").
We have multiple monitoring systems, but because the server was going in and out, they didn't catch the full scope of the issue. This led to a delayed response from our team. Once we diagnosed and fixed the affected server, everything returned to normal.
Our communication
We're normally quick to update everyone when something goes wrong, but this time we let you down. A combination of the delay in detecting the issue, and the timing on Halloween night, meant that we didn't provide updates as we usually would. We're really sorry for the silence -- we know that made the outage more frustrating.
What we're doing now
We're making a few changes to try and avoid an issue of this kind reoccurring in the future, including extra monitoring and alerting, more redundancy in our notifications, and better detection of sudden increases in support volume that might indicate an undetected problem. We'll also make sure we communicate sooner if anything like this happens again.
Thank you
Thanks so much for your patience, and to everyone who reached out to let us know that something wasn't right. We're working to make sure that RTM stays reliable, and that we're communicative when we encounter issues like this.
If you’re still seeing any issues, please let us know. 💙
(Also posted over on the status site.)
Thank you, emily, for responding here, on the status page, and also by e-mail.
Most important for me is "We're working to make sure that RTM stays reliable". That implies to me that RTM won't be developed further, but still kept maintained. For now, that is enough for me.
As I wrote before: I don't want to move to another service - because I like it here.
Most important for me is "We're working to make sure that RTM stays reliable". That implies to me that RTM won't be developed further, but still kept maintained. For now, that is enough for me.
As I wrote before: I don't want to move to another service - because I like it here.
I'm still concerned. Subscription prices went up. The community forums feel abandoned by RTM lately. The feature request forum is dead. And there's zero evidence of any future innovation about RTM to be found, anywhere.
Meanwhile AI is transforming the entire tech landscape.
I still love RTM. But for me to stay 1) there needs to be actual engagement from the RTM team with us users and 2) RTM needs to give us a hint at future evolution of the product.
Meanwhile AI is transforming the entire tech landscape.
I still love RTM. But for me to stay 1) there needs to be actual engagement from the RTM team with us users and 2) RTM needs to give us a hint at future evolution of the product.
We also heard this from Emily in late 2023:
"I'm really sorry for the lack of communication on our end about the Remember The Milk service in general. This one's my fault, and is something we're working to fix right now. You can expect more frequent updates on the blog (and social media, if you're following us there).
I also hear you that we're slow on feature updates and improvements. We've had some big updates (e.g., MilkScript), but I totally appreciate that there are other areas of our apps that people would like to see given some love too. :) We're working to change this -- I realize these are just words, but I'm hoping through our actions that we'll be able to earn your trust back."
*sigh*
"I'm really sorry for the lack of communication on our end about the Remember The Milk service in general. This one's my fault, and is something we're working to fix right now. You can expect more frequent updates on the blog (and social media, if you're following us there).
I also hear you that we're slow on feature updates and improvements. We've had some big updates (e.g., MilkScript), but I totally appreciate that there are other areas of our apps that people would like to see given some love too. :) We're working to change this -- I realize these are just words, but I'm hoping through our actions that we'll be able to earn your trust back."
*sigh*
emily (Remember The Milk) says:
We didn't see any issues on our end today, so please get in touch if you experience any issues!
And I truly appreciate the feedback from everyone.
And I truly appreciate the feedback from everyone.
Log in
to post a reply.