diff --git a/src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md b/src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md
index 2f6cb74cfc..d78145e23f 100644
--- a/src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md
+++ b/src/connections/sources/catalog/libraries/website/javascript/troubleshooting.md
@@ -129,6 +129,10 @@ If you're having issues with your destinations loading with Prototype.js, there
 
 Analytics.js generates a campaign object inside the context object whenever the URL contains search parameters. Without any UTM parameters, the campaign object remains empty. 
 
+## Why do I see events with timestamps in the past or future?
+
+You may see events with timestamp discrepancies due to manual overriding of the timestamp value, mobile apps closed or set in the background, traffic from bots, or inaccurate device or browser time. For more information, see Segment's [Common Fields Spec](/docs/connections/spec/common/#why-are-events-received-with-timestamps-set-in-the-past-or-future).
+
 ## Known issues:
 
 [Review and contribute to these on GitHub](https://github.com/segmentio/analytics.js/issues).