I noticed something very odd that broke something on my end.

The permalink to this comment shows the comment as being two years old, yet the id of the comment is among recent comment ids, which makes no sense to me:

https://www.reddit.com/r/TheEclecticSlide/comments/74s985/you_are_invited/do0qxjo/?st=j9gveiqx&sh=33e6bdf2

Notice that the comment before this one that preceded it (~ 25 days ago):

https://www.reddit.com/r/headphones/comments/74ekx1/rheadphones_tech_support_and_general_help_thread/do0qxjn/

I have never seen this happen before but thought it would be worth bringing up. I'm not sure if there are others like this -- I have to drop a table restraint (which caught this on my end) if I'm going to ingest that comment or I may just ignore it.

Edit: In fact, it isn't just the comment id that is screwed up, the link_id also is messed up. Look at the created_utc values of these two sequential link_ids: https://api.reddit.com/api/info?id=t3_74s985,t3_74s986

It looks like one of your server's clocks is off by two years?

Edit 2: This entire subreddit is wonkers: https://www.reddit.com/r/TheEclecticSlide/

All the submission ids are current (well, within a month) yet the age is 2 years old. So either these are actually two years old and somehow they were created with ids that were 2 years in the future or there is a clock issue? Very strange...I am leaning towards a clock error because the comment id's and link_ids are affected. I'm guessing you shard by subreddit in some way?

No, doesn't look like a clock issue. I honestly don't know what the issue is here. :)

Edit 3: This appears to be the only subreddit like this. I don't see any of the submissions or comments in my dumps, so they weren't around two years ago (at least not publicly). I'm going to wildly guess this may have been a back-up issue or some esoteric bug. Still worth investigating in my opinion.