Holy hell, was shitting bricks, considering I JUST migrated most services to Azure OpenAI (unaffected by outage) — right before our launch about 48 hours back. What a relief.
congrats!
Major outages across ChatGPT and API
211–220 of 617 posts
Re: Major outages across ChatGPT and API
#212Earlier quoted context omitted.
Do you write your refrigerators firmware?
No, but the firmware runs locally, instead of in someone else's cloud, so an outage in their cloud cannot take down my fridge.
Re: Major outages across ChatGPT and API
#213Might as well have a quick discussion here. How's everyone finding the new models? 4-Turbo is a bit worse than 4 for my NLP work. But it's so much cheaper that I'll probably move every pipeline to using that. Depending on the exact problem it can even be comparable in quality/price to 3.5-turbo. However the fact that output tokens are limited to 4096 is a big asterisk on the 128k context.
Here we go with these “it looks worse” just like a month back when people feel it it was worse
Because it was worse.
Re: Major outages across ChatGPT and API
#214I used Google Bard for the first time today specifically because ChatGPT was down. It was honestly perfectly fine, but it has a slightly different tone than ChatGPT that's kind of hard to explain.
Re: Major outages across ChatGPT and API
#215Earlier quoted context omitted.
You can say that about anything, though. BigCorps aren't exactly known for adopting useful tech on a reasonable timeline, let alone at all. I don't think anyone is under the impression that orgs who refuse to migrate off of Java 5 will be looking at OpenAI for anything.
No, this is silly reasoning. A middle manager somewhere has no clue what Java 5 is. But he does know -- or let's say IMAGINES what he knows about ChatGPT. And unlike Java 5-- he just needs to use his departmental budget and instantly mandate that his team now use ChatGPT. Whatever that means you can argue it. But ChatGPT is a front line technology and super accessible. Java 5 is super back end and very specialized. T…
Honest question: do you really mean Java 5 when you say Java 5? It sounds a bit 2000s to me.
Re: Major outages across ChatGPT and API
#216Lots of jokes to be made, but we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI. It took years before most companies who now use cloud providers to trust and be willing to bet their operations on them. That gave the cloud providers time to make their systems more robust, and to learn how to resolve issues quickly.
> Lots of jokes to be made, but we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI.
Gonna be similar (or worse) to what happens when Github goes down. It amazes me how quickly people have come to rely on "AI" to do their work for them.
Re: Major outages across ChatGPT and API
#217Earlier quoted context omitted.
No, this is silly reasoning. A middle manager somewhere has no clue what Java 5 is. But he does know -- or let's say IMAGINES what he knows about ChatGPT. And unlike Java 5-- he just needs to use his departmental budget and instantly mandate that his team now use ChatGPT. Whatever that means you can argue it. But ChatGPT is a front line technology and super accessible. Java 5 is super back end and very specialized. T…
Honest question: do you really mean Java 5 when you say Java 5? It sounds a bit 2000s to me.
Parent used "Java 5" as an example. Java 5 somehow in my mind is from like the 200x era.
But no. I practically mean any complicated back end technology that takes corporations months or years to migrate off of because its quite complicated and requires an intense amount of technical savoir-faire.
My point was that ChatGPT bypasses all this and any middle manager can start using it anywhere for a small hit to his departmental budget.
Re: Major outages across ChatGPT and API
#218I'm imagining a bunch of Tech Priests doing rituals and chanting in front of the data center to encourage the Machine Spirit to restart.
Re: Major outages across ChatGPT and API
#219Earlier quoted context omitted.
What’s your use case? The difference in behavior between the two models seems like it would make failover difficult.
It's really not that different - customers can ask questions about conversations, phone, text, video and typically use that to better understand topics, conversions, sales ops, customer service etc...
fireflies? We've been looking for a tool like this to analyze customer feedback in aggregate (and have been frustrated with Dovetail's lack of functions here)
Re: Major outages across ChatGPT and API
#220Lots of jokes to be made, but we are setting ourselves up for some big rippling negative effects by so quickly building a reliance on providers like OpenAI. It took years before most companies who now use cloud providers to trust and be willing to bet their operations on them. That gave the cloud providers time to make their systems more robust, and to learn how to resolve issues quickly.
I don't think it's so dire. I've gone through this at multiple companies and a startup that's selling B2B only needs one or two of these big outages and then enterprises start demanding SLA guarantees in their contracts. it's a self correcting problem
> enterprises start demanding SLA guarantees
My experience is that SLA "guarantees" don't actually guarantee anything.
Your provider might be really generous and rebate a whole month's fees if they have a really, really, really bad month (perhaps they achieved less than 95% uptime, which is a day and half of downtime). It might not even be that much.
How many of them will cover you for the business you lost and/or the reputational damage incurred while their service was down?