Tracked subprocessors 0 Subprocessor of 0 Third parties loaded 7 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not listed by any tracked vendor.
Not loaded by any published homepage.
Subprocessors None extracted.
Upstox's homepage made 105 requests to 14 domains, and 7 services controlled by another company.
Advertising (3): Google Cloud, Microsoft, X Corp. Analytics (3): Meta, LinkedIn; usually detected as Analytics: AppsFlyer Other (1): Affiliate programs: Trackier 7 third parties by category: Advertising 3 Analytics 3 Other 1
Third parties 7 · 52 requests
Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 30% of the page's requests 31 Microsoft Microsoft Advertising 6% of the page's requests 6 Meta Facebook Pixel 2.9.441 5% of the page's requests 5 X Corp. Twitter Ads 5% of the page's requests 5
LinkedIn Linkedin Insight Tag 3% of the page's requests 3 AppsFlyer appsflyer.com <1% of the page's requests 1 Trackier Trackier <1% of the page's requests 1
First party 1 · 53 requests
Upstox Amazon CloudFront Amazon Web Services HSTS HTTP/3 Next.js 14.2.25 Next.js App Router Open Graph Priority Hints React Webpack core-js 3.32.2 50% of the page's requests 53
5 tracked companies loaded by the homepage are not in Upstox's subprocessor list. A website can use a service without it processing customer data.
What public security catalogs list for Upstox, in their words.
Data breaches Upstox Apr 8, 2021 111,002 accounts Bank account numbers; Dates of birth; Email addresses; Family members' names; Genders; Government issued IDs; Income levels; Marital statuses; Nationalities; Occupations; Passwords; Phone numbers; Physical addresses In April 2021, Indian brokerage firm Upstox suffered a data breach. The incident exposed extensive personal information on over 100k customers including names, genders, dates of birth, physical addresses, banking information and passwords stored as bcrypt hashes. Extensive "know your customer" information was also exposed including scans of bank statements, cheques and identity documents complete with Aadhaar numbers.
Have I Been Pwned Breach data: Have I Been Pwned (CC BY 4.0), which calls every entry a breach, including data scraped from public pages (evidence )
Aug 25: no incident reported Aug 26: no incident reported Aug 27: no incident reported Aug 28: no incident reported Aug 29: no incident reported Aug 30: no incident reported Aug 31: no incident reported Sep 1: no incident reported Sep 2: no incident reported Sep 3: no incident reported Sep 4: no incident reported Sep 5: no incident reported Sep 6: no incident reported Sep 7: no incident reported Sep 8: no incident reported Sep 9: no incident reported Sep 10: 1 incident (1 minor) Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: 2 incidents (2 no impact stated) Sep 16: no incident reported Sep 17: no incident reported Sep 18: no incident reported Sep 19: no incident reported Sep 20: no incident reported Sep 21: no incident reported Sep 22: no incident reported Sep 23: no incident reported Sep 24: no incident reported Sep 25: no incident reported Sep 26: no incident reported Sep 27: no incident reported Sep 28: no incident reported Sep 29: no incident reported Sep 30: no incident reported Oct 1: no incident reported Oct 2: no incident reported Oct 3: no incident reported Oct 4: no incident reported Oct 5: no incident reported Oct 6: no incident reported Oct 7: no incident reported Oct 8: no incident reported Oct 9: no incident reported Oct 10: no incident reported Oct 11: no incident reported Oct 12: no incident reported Oct 13: no incident reported Oct 14: no incident reported Oct 15: no incident reported Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: no incident reported Oct 20: no incident reported Oct 21: no incident reported Oct 22: no incident reported Oct 23: no incident reported Oct 24: no incident reported Oct 25: no incident reported Oct 26: no incident reported Oct 27: no incident reported Oct 28: 1 incident (1 no impact stated) Oct 29: no incident reported Oct 30: no incident reported Oct 31: no incident reported Nov 1: no incident reported Nov 2: no incident reported Nov 3: no incident reported Nov 4: no incident reported Nov 5: no incident reported Nov 6: no incident reported Nov 7: no incident reported Nov 8: no incident reported Nov 9: no incident reported Nov 10: no incident reported Nov 11: no incident reported Nov 12: no incident reported Nov 13: no incident reported Nov 14: no incident reported Nov 15: no incident reported Nov 16: no incident reported Nov 17: no incident reported Nov 18: no incident reported Nov 19: no incident reported Nov 20: no incident reported Nov 21: no incident reported Nov 22: no incident reported 90 days ago today
4 incidents in 90 days0 major or critical24 min typical time to resolveIncidents per month 0 2 4 Dec 2025: 2 incidents (1 major, 1 minor) · typical time to resolve 21 min Jan 2026: 1 incident (1 no impact stated) Feb 2026: 0 incidents Mar 2026: 0 incidents Apr 2026: 1 incident (1 no impact stated) May 2026: 1 incident (1 no impact stated) · typical time to resolve 41 min Jun 2026: 0 incidents Jul 2026: 3 incidents (1 minor, 2 no impact stated) · typical time to resolve 20 min Aug 2026: 1 incident (1 no impact stated) · typical time to resolve 1 h 25 min Sep 2026: 3 incidents (1 minor, 2 no impact stated) · typical time to resolve 7 h 25 min Oct 2026: 1 incident (1 no impact stated) · typical time to resolve 24 min Nov 2026: 0 incidents Dec 2025 Jan 2026 Feb Mar Apr May Jun Jul Aug Sep Oct Nov critical major minor no impact stated
Components affected Component Incidents Bar Order Placement 2
As Upstox's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 28, 2025 (evidence )
None since tracking began.