๊ณ ๊ธ ์ฑ๋ฅ: GoGuardian Admin โ DNS ํํฐ๋ง
- investigating
PM 12:00 PM PDT์ ๊ฒฝ์ฐ GoGuardian Admin DNS ํํฐ๋ง ๋ด์์ ์ง์ฐ ๋ฐ/๋๋ ์คํจํ ํด๊ฒฐ ์๊ฐ์ ๋ณด๊ณ ์์ ์ฆ๊ฐํ์ต๋๋ค. ์ฐ๋ฆฌ์ ํ์ ํ์ฌ ์ด ๋ฌธ์ ๋ฅผ ํด๊ฒฐํ๊ธฐ ์ํด ๋ ธ๋ ฅํ๊ณ ์ฐ๋ฆฌ๊ฐ ์์ ์ ์คํ์ผ๋ก ์ ๋ฐ์ดํธ๋ฉ๋๋ค. ์ฐ๋ฆฌ๋ ์ง์ฌ์ผ๋ก ์ด๋ค ๋ถํธ์ ์ํด ์ฌ๊ณผํฉ๋๋ค.
- investigating
์ด ๋ฌธ์ ๋ฅผ ์กฐ์ฌํ๊ณ ์์ต๋๋ค.
- monitoring
Functionality๋ ์ํฅ์๋ฐ๋ ์ฌ์ฉ์์๊ฒ ๋ณต์๋์์ต๋๋ค. GoGuardian Admin DNS ํํฐ๋ง ์๋น์ค๋ฅผ ์ ๊ทน์ ์ผ๋ก ๋ชจ๋ํฐ๋งํ๊ณ ๋ฌธ์ ์ ์ ๋ฟ๋ฆฌ ์์ธ์ ์กฐ์ฌํ๊ธฐ ์ํด ๊ณ์๋ฉ๋๋ค.
- resolved
This incident has been resolved. Impact: Between approximately 12:00 PM and 2:10 PM PDT on September 8, a subset of GoGuardian Admin DNS Filtering users experienced delayed or failed DNS resolution. Current status: Service returned to normal at approximately 2:10 PM PDT on September 8, and we have observed stability since that time. What we've done: To help prevent this from happening again, our engineering teams have updated the DNS Filtering service infrastructure to better handle unexpected increases in request activity. What's next: Our team is continuing to make improvements to the performance of the DNS Filtering system, and we are keeping a close watch on the service in the meantime. We sincerely apologize for the disruption this caused.
๊ณต์ ์ธ์๋ํธ ์ ๋ฐ์ดํธ๋ฅผ ์๋ ๋ฒ์ญํ์ต๋๋ค.