Is pag.ae down or not working?

What happened to pag.ae, why did the website go down and not work? Here you can see who else is having the same problem with pag.ae, as well as possible solutions. According to our statistics, the following most often do not work: Website, Login, Account, Mobile App.

Current status: No failures

At the moment, according to our data, pag.ae is working fine, but single failures are possible. If pag.ae does not work for you, then report your problem and write a comment.
Add comment

What to do if the site pag.ae is not available? Try our guide.

pag.ae outage reports in the last 24 hours

pag.ae - error and failure reports, troubleshooting methods

Leave your comment describing the failure and share with other users how to solve the problem.
  • No registration required.
  • Messages with obscene language and insults, as well as breaking the law, are not allowed to be published.
  • Active links in the text of the message are not published, but displayed in plain text.
  • It is forbidden to post your own and other people's personal data: addresses, phone numbers, emails, accounts in instant messengers, etc.

Technical information

Main page title:
Link de Pagamento: venda online e receba direto na conta digital PagBank
Main page description:
Com Link de Pagamento você vende online com mais agilidade e facilidade. Crie um link e compartilhe com seus clientes por WhatsApp, redes sociais ou e-mail.
Protocol:
https
Status code:
200
Page size:
167.8 KB
Response time:
2.915sec.
IP:
18.228.108.197
Response headers:
date: Fri, 04 Oct 2024 00:34:54 GMT
content-type: text/html; charset=utf-8
transfer-encoding: chunked
connection: close
cache-control: max-age=60
content-security-policy: child-src *.doubleclick.net *.dynad.net https://www.facebook.com *.hotjar.com *.pagseguro.uol.com.br *.pagbank.com.br *.rm.uol.com.br *.tailtarget.com *.uol.com *.uol.com.br *.youtube.com https://www.google.com *.blip.ai data: 'self'; connect-src *.hotjar.com *.hotjar.io wss://*.hotjar.com *.pagseguro.com.br *.pagbank.com.br *.uol.com.br *.google-analytics.com *.analytics.google.com *.googletagmanager.com *.g.doubleclick.net *.google.com *.google.com.br wss://ws.0mn.io https: wss: 'self'; frame-ancestors 'self'; default-src *.uol.com.br *.pagseguro.com.br *.pagbank.com.br 'self'; media-src *.uol.com.br *.pagseguro.com.br *.pagbank.com.br data: 'self'; object-src *.uol.com.br *.pagseguro.com.br *.pagbank.com.br data: 'self'; font-src *.pagseguro.uol.com.br *.pagseguro.com.br *.pagbank.uol.com.br *.pagbank.com.br *.uol.com *.uol.com.br *.imguol.com.br *.gstatic.com *.hotjar.com https://imguol.com.br data: 'self'; img-src *.google.com *.google.com.br *.google-analytics.com *.analytics.google.com *.googletagmanager.com *.googleapis.com *.gstatic.com *.googleadservices.com *.g.doubleclick.net https://www.facebook.com *.imguol.com *.uol.com *.uol.com.br *.pagseguro.com.br *.pagbank.com.br *.scorecardresearch.com *.ytimg.com *.doubleclick.net *.youtube.com *.hotjar.com *.tailtarget.com bat.bing.com https://imguol.com https://imguol.com.br trg.adilligo.com takenetomni.blob.core.windows.net data: 'self'; script-src bat.bing.com *.doubleclick.net *.dynad.net https://connect.facebook.net *.google-analytics.com *.google.com *.googleadservices.com *.googleapis.com *.googletagmanager.com *.hotjar.com *.jsdelivr.net *.jsuol.com.br *.pagseguro.com.br *.pagbank.com.br *.simg.uol.com.br *.tailtarget.com *.uol.com *.uol.com.br *.ytimg.com https://pagseguro.info https://pag.ae https://imguol.com.br https://www.gstatic.com https://tracking.tunad.io https://js-agent.newrelic.com https://*.nr-data.net about: 'self' 'unsafe-inline' 'unsafe-eval'; style-src *.uol.com *.pagseguro.uol.com.br *.pagseguro.com.br *.pagbank.uol.com.br *.pagbank.com.br *.hotjar.com *.simg.uol.com.br *.ytimg.com https://imguol.com.br 'self' *.google.com *.googleapis.com 'unsafe-inline'; report-uri /csp-report
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=15552000; includeSubDomains
x-download-options: noopen
x-content-type-options: nosniff
vary: Accept-Encoding
x-envoy-upstream-service-time: 369
cf-cache-status: DYNAMIC
set-cookie: __cf_bm=7J4JVkBm2SkjKE3EkcqQDbdHGAd2H4gkclgiWquRdeQ-1728002094-1.0.1.1-k1qSXhfWGHFs5fOOwCpTR79vlXR0trScgzgdtrtusagLNX2PthpBwjuWIejMuIBMtEtUubi8tXEZMR6_uJcUig; path=/; expires=Fri, 04-Oct-24 01:04:54 GMT; domain=.pagseguro.uol.com.br; HttpOnly; Secure; SameSite=None
server: cloudflare
cf-ray: 8cd116c17f765c3a-AMS

SEO headers

h1 PagSeguro
h2 Link de Pagamento: receba pagamentos online na hora
h3 É fácil vender pelas redes sociais e WhatsApp com o PagBank
h3 Confira como criar seu Link de Pagamento
h3 Crie seu link com praticidade em poucos passos
h2 Veja quanto você recebe nas vendas no crédito e parcelado
h3 Aceite pagamentos nos cartões de crédito e débito, via PagBank, Pix e Boleto
h3 Aumente a segurança e potencialize suas vendas!
h3 Pagar com PagBank
h3 Métricas de Aprovação PagBank
h3 Você também pode controlar suas vendas com PagBank
h2 Perguntas frequentes
h3 Ficou com alguma dúvida? Podemos te ajudar!

How to solve problems with pag.ae

Errors on the pag.ae website can be either on the server side or on your side (client side). If there is practically nothing to be done about errors on the server side (it remains only to wait for the site to work again), then with errors on the client side it is possible to solve the problem with the availability of pag.ae on your own.