Tracked subprocessors 0 Subprocessor of 1 Third parties loaded 4 Loaded by 0
+ − ⟲
No tracked subprocessors.
Not loaded by any published homepage.
Subprocessors None extracted.
EBANX's homepage made 103 requests to 8 domains, 4 services controlled by another company, and 1 domain not identified.
Advertising (1): Google Cloud Cookie compliance (1): TrustArc Other (1): reviewed as CMS: Storyblok Unclassified (1): no technology detected from them: Proofpoint 4 third parties by category: Advertising 1 Cookie compliance 1 Other 1 Unclassified 1
Third parties 4 · 66 requests
Storyblok storyblok.com 30% of the page's requests 31 Google Cloud DoubleClick Floodlight Google Analytics Google Tag Manager 26% of the page's requests 27 TrustArc TrustArc 7% of the page's requests 7 Proofpoint urldefense.com <1% of the page's requests 1 Unknown 1 · 1 request
s3-sa-east-1.amazonaws.com
First party 1 · 36 requests
EBANX HSTS Linkedin Ads Next.js 16.2.1 Open Graph React Storyblok Turbopack Vercel Webpack styled-components 6.1.8 35% of the page's requests 36
4 tracked companies loaded by the homepage are not in EBANX's subprocessor list. A website can use a service without it processing customer data.
Aug 15: no incident reported Aug 16: no incident reported Aug 17: no incident reported Aug 18: 1 incident (1 minor) Aug 19: no incident reported Aug 20: no incident reported Aug 21: no incident reported Aug 22: no incident reported Aug 23: 2 incidents (1 major, 1 minor) Aug 24: no incident reported Aug 25: no incident reported Aug 26: no incident reported Aug 27: no incident reported Aug 28: 3 incidents (2 major, 1 minor) 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: 2 incidents (2 minor) 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: no incident reported Sep 11: no incident reported Sep 12: no incident reported Sep 13: no incident reported Sep 14: no incident reported Sep 15: no incident reported 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: 1 incident (1 major) 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: 1 incident (1 major) Sep 30: no incident reported Oct 1: no incident reported Oct 2: 1 incident (1 minor) 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: 1 incident (1 major) 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: 1 incident (1 major) Oct 16: no incident reported Oct 17: no incident reported Oct 18: no incident reported Oct 19: 1 incident (1 major) Oct 20: no incident reported Oct 21: no incident reported Oct 22: no incident reported Oct 23: 1 incident (1 critical) Oct 24: no incident reported Oct 25: no incident reported Oct 26: no incident reported Oct 27: 1 incident (1 major) Oct 28: no incident reported Oct 29: 1 incident (1 critical) 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: 1 incident (1 major) Nov 5: no incident reported Nov 6: 1 incident (1 critical) Nov 7: no incident reported Nov 8: no incident reported Nov 9: no incident reported Nov 10: 2 incidents (2 major) Nov 11: 1 incident (1 critical) Nov 12: no incident reported 90 days ago today
22 incidents in 90 days16 major or critical1 h 44 min typical time to resolve36 h 46 min longest majorIncidents per month 0 4 8 Dec 2025: 6 incidents (2 major, 4 minor) · typical time to resolve 1 h 48 min Jan 2026: 3 incidents (2 major, 1 no impact stated) · typical time to resolve 46 min Feb 2026: 5 incidents (2 critical, 2 major, 1 minor) · typical time to resolve 4 h 12 min Mar 2026: 4 incidents (2 major, 1 minor, 1 no impact stated) · typical time to resolve 35 min Apr 2026: 3 incidents (1 critical, 1 major, 1 minor) · typical time to resolve 44 min May 2026: 7 incidents (1 critical, 3 major, 3 minor) · typical time to resolve 1 h 17 min Jun 2026: 5 incidents (1 critical, 2 major, 2 minor) · typical time to resolve 2 h 42 min Jul 2026: 8 incidents (1 critical, 5 major, 2 minor) · typical time to resolve 29 min Aug 2026: 8 incidents (4 major, 4 minor) · typical time to resolve 51 min Sep 2026: 4 incidents (2 major, 2 minor) · typical time to resolve 2 h 47 min Oct 2026: 7 incidents (2 critical, 4 major, 1 minor) · typical time to resolve 2 h 13 min Nov 2026: 5 incidents (2 critical, 3 major) · typical time to resolve 16 min 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 Cash 3 E-Wallet 3 PIX 3 Bank Transfer 2 Cards (credit/debit) 1 PagoEfectivo 1 Payments API 1
As EBANX's status page reports its own incidents (scheduled maintenance left out), read every few hours since Oct 1, 2025 (evidence )
None since tracking began.