ReadMe

readme.com

ReadMe declares 15 subprocessors in its subprocessor list, which we last checked on Nov 11, 2026 (evidence). They include Amazon Web Services, Google Cloud and OpenAI. No published changes since we first read it on Sep 22, 2026. 10 tracked vendors name ReadMe as a subprocessor, including PagerDuty, ClickUp™ and Badge.

Subprocessors CSV of ReadMe's subprocessors · Atom feed of ReadMe's subprocessors DORA draft CSV of ReadMe's subprocessors as declared by ReadMe what's this? · 

15 third parties.

NamePurposeLocationListed since
Algolia Application Search HostingUSA
Anthropic AIArtificial IntelligenceUSA
AWS Data HostingUSA
Baremetrics Payment AnalyticsUSA
Cloudflare Network Security, CDNUSA
Google Gemini AIArtificial IntelligenceUSA
Heroku Application HostingUSA
Hubspot Marketing AutomationUSA
MongoDB Database HostingUSA
Okta Identity and access managementUSA
OpenAI AIArtificial intelligenceUSA
Render Application HostingUSA
Salesforce CRMUSA
Segment Customer AnalyticsUSA
Stripe PaymentsUSA

Web TechnologiesCSV of ReadMe's web technologies · Atom feed of ReadMe's web technologies

ReadMe's homepage made 277 requests to 24 domains, and 9 services controlled by another company.

Analytics (4): HubSpot, Amplitude, LinkedIn, MetaAdvertising (2): Google Cloud, Reddit, Inc.Live chat (1): reviewed: IntercomCDN (1): jsDelivrOther (1): Font scripts: Font Awesome

9 third parties by category: Analytics 4Advertising 2Live chat 1CDN 1Other 1

Third parties 9 · 56 requests
Google Cloudsubprocessor DoubleClick Floodlight Google Analytics Google Tag Manager 6% of the page's requests 18
HubSpotsubprocessor HubSpot HubSpot Analytics 5% of the page's requests 13
Font Awesome Font Awesome 2% of the page's requests 6
Intercom intercom.io, intercomcdn.com 2% of the page's requests 6
Amplitude Amplitude 1% of the page's requests 4
LinkedIn Linkedin Insight Tag 1% of the page's requests 3
Meta Facebook Pixel 2.9.435 1% of the page's requests 3
Reddit, Inc. Reddit Ads <1% of the page's requests 2
jsDelivr jsDelivr <1% of the page's requests 1
First party 1 · 221 requests
ReadMe Framer Motion HSTS Intercom Next.js 16.3.3 Next.js App Router Open Graph Priority Hints React Three.js 182 Turbopack Vercel Webpack core-js 3.32.2 80% of the page's requests 221

5 tracked companies loaded by the homepage are not in ReadMe's subprocessor list. A website can use a service without it processing customer data.

Subprocessor of (10)CSV of the companies listing ReadMe · Atom feed of the companies listing ReadMe

10 companies

ComplianceCSV of ReadMe's compliance · Atom feed of ReadMe's compliance

Certified
Says it complies with

Certifications as ReadMe's trust center lists them; reports are usually shared on request (evidence)

Service statusCSV of ReadMe's status page incidents · Atom feed of ReadMe's status page incidents

Aug 15: no incident reportedAug 16: no incident reportedAug 17: no incident reportedAug 18: no incident reportedAug 19: no incident reportedAug 20: no incident reportedAug 21: 1 incident (1 minor)Aug 22: no incident reportedAug 23: no incident reportedAug 24: no incident reportedAug 25: no incident reportedAug 26: no incident reportedAug 27: no incident reportedAug 28: no incident reportedAug 29: no incident reportedAug 30: no incident reportedAug 31: no incident reportedSep 1: no incident reportedSep 2: no incident reportedSep 3: no incident reportedSep 4: no incident reportedSep 5: no incident reportedSep 6: no incident reportedSep 7: no incident reportedSep 8: 1 incident (1 critical)Sep 9: no incident reportedSep 10: no incident reportedSep 11: no incident reportedSep 12: no incident reportedSep 13: no incident reportedSep 14: no incident reportedSep 15: no incident reportedSep 16: no incident reportedSep 17: no incident reportedSep 18: no incident reportedSep 19: no incident reportedSep 20: no incident reportedSep 21: no incident reportedSep 22: 1 incident (1 minor)Sep 23: no incident reportedSep 24: no incident reportedSep 25: no incident reportedSep 26: no incident reportedSep 27: no incident reportedSep 28: no incident reportedSep 29: no incident reportedSep 30: no incident reportedOct 1: no incident reportedOct 2: no incident reportedOct 3: no incident reportedOct 4: no incident reportedOct 5: no incident reportedOct 6: no incident reportedOct 7: no incident reportedOct 8: no incident reportedOct 9: no incident reportedOct 10: no incident reportedOct 11: no incident reportedOct 12: no incident reportedOct 13: no incident reportedOct 14: 1 incident (1 critical)Oct 15: no incident reportedOct 16: no incident reportedOct 17: no incident reportedOct 18: no incident reportedOct 19: no incident reportedOct 20: no incident reportedOct 21: no incident reportedOct 22: no incident reportedOct 23: 1 incident (1 major)Oct 24: no incident reportedOct 25: no incident reportedOct 26: no incident reportedOct 27: no incident reportedOct 28: no incident reportedOct 29: no incident reportedOct 30: no incident reportedOct 31: no incident reportedNov 1: no incident reportedNov 2: 1 incident (1 no impact stated)Nov 3: no incident reportedNov 4: no incident reportedNov 5: no incident reportedNov 6: no incident reportedNov 7: no incident reportedNov 8: no incident reportedNov 9: no incident reportedNov 10: no incident reportedNov 11: no incident reportedNov 12: no incident reported

90 days agotoday

  • 6 incidents in 90 days
  • 3 major or critical
  • 1 h 40 min typical time to resolve
  • 23 min longest major
BeganIncidentImpactLasted
Degraded performance on documentation sitesno impact stated1 h 40 min
Elevated 503 Errors and Documentation Availabilitymajor23 min
Projects are not loadingcritical11 min
Degraded Performance Across Hubsminor2 h 21 min
Admin interface outagecritical11 min
Slow search within customer hubsminor1 h 45 min
Degraded performance due to third-party infrastructure issuesminor1 h 15 min
API Reference Degradationno impact stated2 h 41 min

Incidents per month

0 4 8 Dec 2025: 2 incidents (1 major, 1 minor) · typical time to resolve 1 h 23 min Jan 2026: 0 incidents Feb 2026: 0 incidents Mar 2026: 2 incidents (1 major, 1 minor) · typical time to resolve 24 min Apr 2026: 8 incidents (1 critical, 2 major, 5 minor) · typical time to resolve 2 h 54 min May 2026: 7 incidents (2 critical, 3 major, 2 minor) · typical time to resolve 6 h 55 min Jun 2026: 1 incident (1 no impact stated) · typical time to resolve 2 h 41 min Jul 2026: 1 incident (1 minor) · typical time to resolve 1 h 15 min Aug 2026: 1 incident (1 minor) · typical time to resolve 1 h 45 min Sep 2026: 2 incidents (1 critical, 1 minor) · typical time to resolve 2 h 21 min Oct 2026: 2 incidents (1 critical, 1 major) · typical time to resolve 23 min Nov 2026: 1 incident (1 no impact stated) · typical time to resolve 1 h 40 min Dec 2025Jan 2026Feb Mar Apr May Jun Jul Aug Sep Oct Nov

critical major minor no impact stated

Components affected

ComponentIncidentsBar
ReadMe Hubs5
Admin Dashboard4
ReadMe Knowledge Base2
Developer Metrics1

As ReadMe's status page reports its own incidents (scheduled maintenance left out), read every few hours since (evidence)

Incidents reported by ReadMe's subprocessorsCSV of incidents reported by vendors ReadMe lists · Atom feed of incidents reported by vendors ReadMe lists

259 reported incidents in the last 30 days, by 7 of the vendors ReadMe lists as subprocessors.

A subprocessor list names a company, not the service an incident touched. This does not show that ReadMe was involved.

DateCompanyIncidentImpactLasted
SegmentMMS Delivery Failures from Twilio to GCI United States minor3 min
SegmentSMS Delivery Failures from Twilio 10DLC to AT&T United States minor4 h 3 min
SegmentSMS Delivery Failures from Twilio to Orange Sierra Leone minorongoing
SegmentSMS Delivery Failures From Long Code Numbers to AT&T in the US minor1 h 19 min
SegmentSMS Delivery Delays from Twilio to MTS Kazakhstan minorongoing
SegmentSMS Delivery Failures from a Subset of Twilio Phone Numbers to Tcell Tajikistan minorongoing
OpenAIUnable to start new Workspace Agent runs criticalongoing
SegmentMMS Delivery Delays from a Subset of Twilio Long Codes to Multiple Small Networks in United States minorongoing
SegmentSMS Delivery Failures from a Subset of Twilio Phone Numbers to K-Cell Kazakhstan minor7 h 23 min
OpenAIElevated errors affecting logins, sign-ups, and ChatGPT features minor8 min
SegmentVoice Call Failures in JP1 minor3 h 51 min
SegmentOn Call Engineers are Investigating no impact statedongoing
RenderAPI Performance Issues minor18 min
SegmentSMS Delivery Failures from Twilio to Turkcell Turkey minor3 h 54 min
SegmentRetroactive Incident Impacting Twilio Usage APIs no impact stated1 min
AnthropicElevated errors on Fable 52 and Mythos 52 no impact stated1 min
SegmentIssue resolved minor1 h 43 min
SegmentSMS Delivery Receipt Delays from Twilio Phone Numbers to Movistar Venezuela minor3 h 26 min
HubSpotSome HubSpot tools may be unavailable for some users no impact stated51 min
SegmentGateway API (Lookup API) Failure Increase on Verizon in United States minor10 h 23 min
OpenAIIncorrect cost data in Costs API exports no impact stated2 h 20 min
OpenAIElevated Errors On API minor42 min
SegmentWhatsApp Business API Message Send Failures minor16 h 29 min
OpenAIElevated ChatGPT Conversation Errors minor52 min
SegmentVoice Call Failures from a Subset of Twilio Phone Numbers to Chile minor19 h 20 min

And 234 more. All of them: CSV · Who is around them.

ChangesCSV of ReadMe's changes · Atom feed of ReadMe's changes

See the list as we read it on any date: Time machine

None since tracking began.

Rating badge for ReadMe's site

ReadMe transparency rating

It updates with the rating.

<a href="https://thirdpartyindex.com/vendors/readme"><img src="https://thirdpartyindex.com/badge/readme.svg" alt="ReadMe transparency rating on Third Party Index" height="20"></a>
[![ReadMe transparency rating on Third Party Index](https://thirdpartyindex.com/badge/readme.svg)](https://thirdpartyindex.com/vendors/readme)