#Llama 3.1 8b Groq provider issue

1 messages · Page 1 of 1 (latest)

magic lagoonBOT
#

@scarlet frigate

Description:
Lately the Groq provider (selected via :nitro) is outputting gibberish until max tokens. Was working fine previously so this is a provider issue. Please derank them or let them know.

What I've Tried:
Switching provider by removing :nitro solves the issue. It's a groq problem.

Error Messages:

followInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitInitIn

API/Model: meta-llama/llama-3.1-8b-instruct:nitro

#

I'm an AI assistant - my answers may be incorrect and I cannot see screenshots. Please verify information with the OpenRouter docs.

Thank you for the detailed report and troubleshooting steps. To help the support/mod team investigate and escalate this Groq provider issue for meta-llama/llama-3.1-8b-instruct:nitro, could you please provide:

  • The full API response (including any headers if possible) when the gibberish output occurs
  • The exact prompt or code snippet you used that triggers this issue
  • Approximately when the issue started (date/time, if known)

OpenRouter routes requests to providers based on your selection and can reroute if there are problems, but accurate logs and reproduction steps are required to escalate provider issues effectively. You can learn more about provider routing at Provider Routing.

Once you provide this information, mods can review and potentially contact Groq or adjust routing as needed.

-# This is an automated response powered by Answer HQ. Use !mute to stop the bot from responding, or !close when your question is resolved.