November 15, 2024 Deepgram Maintenance Window FAQ

What’s happening?

Deepgram has scheduled maintenance for November 15, 2024 from 4-7AM UTC to improve the performance of our management APIs.

What services will be affected during the maintenance window?

• console.deepgram.com Unavailable.

  • Customers will not be able to log in, view usage charts/logs, create API keys, or access billing information.

• API Playground (playground.deepgram.com): Unavailable.

• Management APIs: Unavailable

  • Projects: Get, update, and delete projects.

  • API Key Management: Create, delete, and get API keys.

  • Member Management: View, remove, and manage member scopes, invitations, and project access.

  • Usage: View request data, usage summaries, and fields.

  • Billing: View balances.

  • Models: View model metadata.

Will the speech to text, text to speech, audio intelligence, text intelligence and voice agent APIs be down?

No. Customers will be able to access our /v1/listen, /v1/read, /v1/speak, and /v1/agent endpoints with existing API keys.

Will I be able to create API keys during the migration?

No. Creating API keys using Console or the API will be down during the migration.

If you use temporary keys for client-side authentication, you have 3 options:

1. If you have client-side authentication through a secure backend, start proxying audio through your backend instead of sending it straight to Deepgram from your frontend. The Node SDK supports this.

   1. This will allow you to create a longer-lasting API key and rotate much less frequently.

   2. Make sure your API key will not expire (or need to be recreated) during the maintenance period.

2. Extend the expiration time of your temporary keys beyond the maintenance window

   1. Make sure your key rotation is scheduled to not need to occur during or immediately after the maintenance period

   2. This means you should extend the expiration time of your temporary key to > 2 hours and ensure that they rotate before the maintenance period and will not expire during the maintenance period.

  //Make sure rotation occurs just before the maintenance period to
  //avoid it expiring during the maintenance period.

    let { result: newKeyResult, error: newKeyError } =
    await deepgram.manage.createProjectKey(project.project_id, {
      comment: "Temporary API key",
      scopes: ["usage:write"],
      tags: ["next.js"],
      time_to_live_in_seconds: 7200, //Set this to be > 2 hours 
    });

1. If the above solutions are not possible, prepare for an outage during our maintenance period. This could include:

   1. Turning off certain features of your application that rely on Deepgram during the maintenance period

   2. Implementing caching or other fallback experiences if you are unable to connect to Deepgram during the maintenance period

   3. Adding warning banners or error messages for customers to let them know things will be back after the maintenance period.

Will Deepgram Docs be unavailable?

No, developers.deepgram.com will not be impacted.

How can I get updates during the upgrade?

We will provide real-time updates through our status page. We’re committed to ensuring this process goes as smoothly as possible and will communicate promptly if any additional information arises.

I have another question.

• Ask a question on our dedicated GitHub discussions thread.

• Or ask a question in our Discord Community