-------- Thu, September 3, 2026 5:39 JST - Thu, September 3, 2026 7:39 JST Some users were experiencing difficulties in making and receiving phone calls by MiiTel Phone using Circuit Type JPN-1. We apologize for any inconvenience this may cause.
■ Date and time: ・Thu, September 3, 2026 5:39 JST - Thu, September 3, 2026 7:39 JST
■ Affected services: ・MiiTel Phone ・MiiTel Phone Mobile
■ Circuit Type: ・JPN-1 ※ Please check your Circuit Type at MiiTel Admin > Phone Number > Phone Number List
--------- We would like to inform you that as of Thu, September 3, 2026, some users are experiencing difficulties in making and receiving phone calls by MiiTel Phone using Circuit Type JPN-1. Currently, we are investigating this issue. We apologize for any inconvenience caused.
■ Date and time: ・Thu, September 3, 2026 5:40 JST - Current
■ Affected services: ・MiiTel Phone ・MiiTel Phone Mobile
■ Circuit Type ・JPN-1 ※ Please check your Circuit Type at MiiTel Admin > Phone Number > Phone Number List
------- 31, Aug Mon, 2026, 10:45 AM – 31, Aug Mon, 2026, 11:10 AM JST Some users experienced issues integrating with kintone due to a service outage on kintone. The issue has now been resolved, and the services are available as usual. We sincerely apologize for any inconvenience caused.
■ Date and time: ・31, Aug Mon, 2026, 10:45 AM – 31, Aug Mon, 2026, 11:10 AM JST
■ Details: ・Contacts may not have been synced with kintone ・Activity history may not have been registered in kintone ・Meeting history may not have been registered in kintone
■ Additional information: Contacts were not retrieved from kintone, and activity history was not registered in kintone. Please take the following actions:
---------------------- ・Call activity history integration Please manually register the activity history from MiiTel Phone Analytics.
・Contact integration ・Meeting history integration We apologize for the inconvenience, but please register the information manually. ----------------------
You can review any errors that occurred during the period when kintone integration was unavailable on the Third-Party Integration Error Log screen.