Are you having issues? Provide feedback to Jugem by selecting the option you are having issues with.
HTTP/1.1 200 OK Server: nginx/1.18.0 Date: Wed, 09 Feb 2022 08:49:03 GMT Content-Type: text/html; charset=UTF-8 Transfer-Encoding: chunked Connection: keep-alive Cache-Control: private, must-revalidate pragma: no-cache expires: -1 Set-Cookie: XSRF-TOKEN=eyJpdiI6ImpKN1pYejZ3SkQ1NFwvTXN1clFCNkFBPT0iLCJ2YWx1ZSI6IlduMWkzVGZJbzkxalNBa3V0VkVlb1BWNkdHakZoSW5KdWVwZDkyNFN0WU5VSFkwSUFlM0FKcnp4YnVucGpnZnVYMEZheHFlVHAzQnlEOUVLclJVNzN3PT0iLCJtYWMiOiIyYzBiYjE1YTRhODVjODc2NzNjYjZhNzMwODk2ZmNmNTM4MTZjMWFhNTlhNDAyMGI3MTgwMjlhMTZkYmFhNTM2In0%3D; expires=Wed, 09-Feb-2022 10:49:03 GMT; Max-Age=7200; path=/ Set-Cookie: laravel_session=eyJpdiI6ImRrMFo5MHFlQ3VNMUJlajJzWXBXY2c9PSIsInZhbHVlIjoiZ0hjWk83c2RDV0dJamNZSW9CbFJWR2ljU3RXVEs1b3JMU1RzZnRUaVFKZ1JnVVNSR0F6RzBneG41TEJKUWJGMmF3czJEQjdjdTA0ZWhja2pHVU45Mnc9PSIsIm1hYyI6ImVmZTM1M2JhODgyNzE1OGE1MTdlZDQwZDNkNmYyMGEyMmYyM2Y1ZDU5NDgxOWNhYzM2NDlhYTJhYTFlODYzY2UifQ%3D%3D; expires=Wed, 09-Feb-2022 10:49:03 GMT; Max-Age=7200; path=/; httponly Vary: Accept-Encoding Strict-Transport-Security: max-age=63072000
The DNS is up. We have tried pinging Jugem.jp. There are no DNS Issues detected!
Type | Name | Value | Class | TTL |
A | jugem.jp | 35.72.144.125 | IN | 299 |
A | jugem.jp | 35.74.206.212 | IN | 299 |
NS | jugem.jp | IN | 300 | |
NS | jugem.jp | IN | 300 |
We have tried pinging Jugem.jp using our servers and the Jugem.jp server responded on time, indicating that there are no current Jugem.jp problems today.
If Jugem.jp is down for you too, the server might be overloaded or unreachable because of network problems, outages or a website maintenance is in progress.
If Jugem.jp is UP for us but you cannot access it, try these solutions: