https://misaka.fail

Misaka Network, Inc. StatusWelcome to Misaka Network, Inc.'s home for real-time and historical data on system performance.Misaka Network, Inc. Status x Get email notifications whenever Misaka Network, Inc. creates, updates or resolves an incident. Email address: Enter OTP: Resend OTP in: seconds Didn't receive the OTP? Resend OTP This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Get incident updates and maintenance status messages in Slack. Subscribe via Slack By subscribing you agree to the Atlassian Cloud Terms of Service and acknowledge Atlassian's Privacy Policy. Follow @AS57695 or  view our profile. Get the Atom Feed or RSS Feed. Hypervisor down in AMS5 Subscribe Investigating - We are currently investigating this issue. Nov 07, 2024 - 22:13 UTC × Subscribe to Incident Subscribe to updates for Hypervisor down in AMS5 via email. You'll receive email notifications when incidents are updated. VIA EMAIL: Subscribe to Incident This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply. Public API Operational Cloud Servers Operational Object Storage Operational Block Storage Operational Package Mirrors Operational Authoritative DNS Operational Recursive DNS Operational DNS Updates Operational Analytics Operational SDN Controller Operational Mail Queue Operational Legacy Services Operational SolusVM Master Operational Metadata Service (Legacy) Operational WHMCS (ZeptoVM) Operational Datacenters Degraded Performance Ashburn, VA, United States - (IAD01) Operational Secaucus, NJ, United States - (EWR02) Operational Kansas City, MO, United States - (MCI01) Operational Seattle, WA, United States - (SEA02) Operational Los Angeles, CA, United States - (LAX07) Operational Montréal, QC, Canada - (MTL03) Operational São Paulo, Brazil - (SAO03) Operational Amsterdam, Netherlands - (AMS03) ? Operational Amsterdam, Netherlands - (AMS05) ? Degraded Performance Frankfurt, Germany - (FRA08) ? Operational London, United Kingdom - (LON07) ? Operational Madrid, Spain - (MAD02) Operational Milan, Italy - (MIL01) Operational Prague, Czech Republic - (PRG01) Operational Sofia, Bulgaria - (SOF01) Operational Stockholm, Sweden - (STO01) Operational Oslo, Norway - (OSL01) Operational Moscow, Russia - (MOW01) ? Operational Khabarovsk, Russia - (KHV01) Operational Tokyo, Japan - (NRT04) ? Operational Hong Kong - (HKG12) ? Operational Seoul, South Korea - (ICN05) Operational Johannesburg, South Africa - (JNB01) Operational Singapore - (SIN03) Operational San Jose, CA, United States - (SJC10) Operational Marseille - France (MRS01) Operational Lagos, Nigeria - (LOS02) Operational Berlin, Germany (BER02) Operational Taipei (TPE01) Operational Berlin, Germany (BER03) ? Operational External Services Operational Cloudflare CDN Operational Mailgun Operational Stripe API Operational Operational Degraded Performance Partial Outage Major Outage Maintenance Past Incidents Nov 8, 2024 No incidents reported today. Nov 7, 2024 Connectivity issues in Berlin (BER02, BER03) Resolved - This incident has been resolved. Nov 7, 08:29 UTC Identified - We've noticed that one of our core routers in BER02 is currently rebooting abnormally. The equipment has been isolated from our network and the connection to NL-IX / Joint Transit will be temporarily unavailable until the equipment is back online. Latency to some networks may be higher than usual during the outage. Oct 31, 07:01 UTC Nov 6, 2024 No incidents reported. Nov 5, 2024 Scheduled Network Maintenance in Taipei (TPE01) Resolved - The scheduled maintenance has been completed. Nov 5, 16:33 UTC Update - We experienced an unexpected reboot of our secondary router during the migration. The router is currently recovering, but BGP convergence may take approximately 15 minutes. Nov 5, 15:20 UTC Identified - The issue has been identified and a fix is being implemented. Nov 5, 15:05 UTC Scheduled Network Maintenance in Taipei (TPE01) Completed - The scheduled maintenance has been completed. Nov 5, 15:00 UTC Update - HINET domestic peering will be temporarily moved to tw-tpe1-cr2a. Latency to HINET may increase during the migration. Nov 5, 09:47 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Nov 5, 09:00 UTC Scheduled - Date: November 5, 2024Maintenance Window: 17:00 - 23:00 Taipei local time (UTC+8)Maintenance impact: up to 4 hoursExpected downtime: up to 10 minutesWe will be replacing our tw-tpe1-cr1a core router. This upgrade will increase the capacity of our network and improve the overall performance of our services; during the maintenance window, traffic previously terminated on tw-tpe1-cr1a will be rerouted to ensure no downtime, but some latency may be higher than normal. Affected resources are listed below:- Taipei-Hong Kong backbone- China optimized routes via Hong Kong- HINET domestic peering- TPIX peering portIP Transit customers terminated on tw-tpe1-cr1a will be notified separately.We apologize for any inconvenience this may cause and appreciate your patience as we work to improve our network infrastructure. Nov 4, 19:22 UTC Nov 4, 2024 No incidents reported. Nov 3, 2024 No incidents reported. Nov 2, 2024 No incidents reported. Nov 1, 2024 No incidents reported. Oct 31, 2024 Scheduled Maintenance in Seattle, WA (SEA02) Resolved - This incident has been resolved. Oct 31, 13:51 UTC Monitoring - Verification is currently underway for the maintenance items. Oct 31, 13:33 UTC Identified - Our upstream is currently working on a major infrastructure upgrade. We anticipate connectivity outages on all servers for up to a maximum of 30 minutes during the maintenance window. Oct 31, 13:24 UTC Oct 30, 2024 Scheduled Network Maintenance in Los Angeles (LAX02) Completed - The scheduled maintenance has been completed. Oct 30, 09:35 UTC Verifying - Verification is currently underway for the maintenance items. Oct 30, 09:23 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 30, 00:40 UTC Scheduled - We will be migrating our connections to the CN connectivity provider and upgrading capacity; during this maintenance, connectivity to CN will be rerouted to alternative providers. Oct 30, 00:35 UTC Oct 29, 2024 Scheduled Network Maintenance in Berlin, Germany (BER02, BER03) Completed - The scheduled maintenance has been completed. Oct 29, 17:00 UTC Verifying - Verification is currently underway for the maintenance items. Oct 29, 16:25 UTC In progress - Scheduled maintenance is currently in progress. We will provide updates as necessary. Oct 29, 13:00 UTC Scheduled - We would like to inform you about an upcoming network maintenance in our Berlin datacenters.We will be upgrading our backbone capacity between Speedbone and 3U Telecom in Berlin. This upgrade will increase the capacity of our network and improve the overall performance of our services, during the maintenance window the traffic will be rerouted to ensure no downtime but some latency may be higher than normal.We apologize for any inconvenience this may cause and appreciate your patience as we work to improve our network infrastructure. Oct 27, 19:15 UTC Oct 28, 2024 No incidents reported. Oct 27, 2024 No incidents reported. Oct 26, 2024 Connectivity issues in Los Angeles (LAX02) Resolved - This incident has been resolved. Oct 26, 17:41 UTC Identified - We are currently working to resolve a hardware issue with our edge router that is randomly rebooting. This router is located in a network POP with limited power capacity, which unfortunately lacks redundancy. As a result, when the router fails, CN customers are rerouted to alternative carriers.We have ordered a replacement and additional spares and expect this to be operational by 1 October. We will keep you updated on our progress and appreciate your patience as we work to resolve this matter.Thank you for your understanding. Sep 23, 20:15 UTC China Connectivity issues in Asia (HKG12, TPE01, SIN03) Resolved - This incident has been resolved. Oct 26, 17:40 UTC Update - The metro connection in Singapore has been completed, and we’ve rerouted the remaining destinations to ChinaNet. If you continue to experience connectivity issues, please provide an MTR report with both the source and destination IP addresses. This will help us assess whether further rerouting through other carriers we partner with could optimize your connection.Currently, we do not have an estimated time for full service recovery. We appreciate your patience and will keep you updated with any new developments.Thank you for your understanding. Oct 18, 05:47 UTC Update - Most paths have been rerouted, and the packet loss issue should now be resolved, except for Singapore where we're currently waiting for a metro connection to be completed.If you continue to experience connectivity issues, please send us an MTR report that includes both the source and destination IP addresses. This information will help us determine if rerouting through other carriers we work with can optimize your connection. Oct 16, 12:47 UTC Identified - We are currently experiencing a disruption with our connectivity provider for CN routes. We are actively working to establish additional connections to restore service. During this time, you may notice increased latency. We appreciate your patience and understanding as we work to resolve this issue.If you have any questions or need further assistance, please do not hesitate to contact us. Oct 15, 07:41 UTC Oct 25, 2024 No incidents reported. ← Incident History Powered by Atlassian Statuspageenen1731034141https://misaka.fail

ތިޔަ ސައިޓް އެޑިޓް ކުރަންވީތަ؟

ތިބާ ކީއްކުރަނީ؟