We've noticed that the Statuspage RSS is using "pubDate" as the "change date", this is confusing some feed readers since "pubDate" is meant to be used to timestamp when a post was posted, ref. RSS 2.0 Specification (Current)
Is this an indended use because of limitations in RSS, or is it an error?
I'm no expert on RSS, but the RSS validator also remarks pubdates as "implausible dates" because it is set in the future. RSS Validator Results: https://status.nhn.no/history.rss
Hey Aleksander,
Thanks for reaching out to Atlassian Community!
It's a really good observation and you're right to question how the pubDate
field is being used in the Statuspage RSS feed.
In the RSS 2.0 specification, the pubDate
is meant to reflect when the item was published — for example, when a blog post or news article goes live. However, in the Statuspage RSS feed, pubDate
is currently used to show the scheduled timeor the last updated time of a maintenance or incident, even if that time is in the future.
This approach isn't fully aligned with the RSS specification. As a result, some feed readers or RSS validators might see this as a problem — especially when the pubDate
is set in the future. That's likely why you're seeing warnings like “implausible dates” in your RSS validator.
That said, this is currently expected behavior in Statuspage. The reason is that RSS doesn't offer a separate field for things like "event start time" or "last update." So the pubDate
field is reused to make sure feed readers display upcoming events in a useful way — even if it’s technically outside of spec.
We’ve seen this feedback before and it’s something we’ve passed along internally. Ideally, it could be improved in the future — for example, by introducing custom elements or handling timestamps differently — but for now, it’s working this way by design.
Hope this helps clarify things!
Best Regards,
Egor
Thanks! This is no big issue for us, we'll find some feed readers to recommend for our users.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.