Results 1 to 2 of 2
  1. #1
    NOC NOC_NA's Avatar
    Join Date
    May 2011
    Location
    Hidden
    Posts
    6,867

    Regarding Issues with Moving to Instanced Content in Chaos Data Center (Jun. 24)

    Due to the heavy congestion of access requests to instanced content, we are currently experiencing issues where players are unable to enter instanced content on the Chaos Data Center.

    We are currently investigating the cause of the issue and implementing measures to resolve it.

    We apologize for any inconvenience this may be causing, and we thank you for your patience and understanding.        

    [Date & Time]
    From Jun. 24, 2017 8:47 a.m. (PDT)
    From Jun. 24, 2017 15:47 (GMT)
    From Jun. 24, 2017 16:47 (BST)

    [Issue Details]
    ・Unable to enter instanced content.

    [Cause]
    Under investigation

    [Affected Worlds]
    All Chaos data center Worlds:
    ・Cerberus
    ・Lich
    ・Louisoix
    ・Moogle
    ・Odin
    ・Omega
    ・Phoenix
    ・Ragnarok
    ・Shiva
    ・Zodiark
    (0)

  2. #2
    NOC NOC_NA's Avatar
    Join Date
    May 2011
    Location
    Hidden
    Posts
    6,867

    Regarding Issues with Moving to Instanced Content in Chaos Data Center (Jun. 24, 25)

    We have confirmed that the issue wherein players are unable to enter instanced content on the Chaos Data Center due to heavy congestion has been resolved.

    We will continue to investigate the cause and more information will be provided as the situation develops.

    [Date & Time]
    Jun. 24, 2017 8:47 a.m. to 7:00 p.m. (PDT)
    Jun. 24, 2017 15:47 to Jun. 25, 2017 2:00 (GMT)
    Jun. 24, 2017 16:47 to Jun. 25, 2017 3:00 (BST)

    [Details]
    ・Unable to enter instanced content

    [Cause]
    Under investigation

    [Affected Worlds]
    All Chaos data center Worlds

    *Edited Jul. 6, 2017 7:50 p.m. (PDT)
    Countermeasures to the issue described above were implemented during the maintenance from Jul. 3, 2017 10:00 p.m. to Jul. 4, 2017 2:10 a.m. (PDT).
    We apologize for any inconvenience this may have caused.
    (0)