Arize
Arize is an AI observability and model monitoring platform serving data scientists and ML engineers tracking model performance.
About this data
Updated June 29, 2026
Overall Pulse Score
-2 over this period
A 0-100 index summarizing the tone of 178 relevant public mentions gathered from public online communities across 12 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Weekly Sentiment Trend
Pulse Score by week over the selected period. Each point is one complete week of mentions.
This week in public discussion
Discussion around Arize over the recent period leaned negative, with bug reports and reliability concerns drawing the most attention among commenters. Several mentions flagged specific instrumentation issues, including span data being overwritten and token counts being mapped incorrectly, which some users connected to concerns about downstream cost calculations. A smaller share of discussion praised features and integrations, and a couple of mentions noted Arize Phoenix appearing in an external observability tool directory. Overall sentiment appeared to soften slightly compared to the prior period.
Read the deeper analysisAI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Sentiment mix by week
How the tone of public discussion splits each week.
Most-discussed praise
Most-discussed complaints
Themes across the selected period, with mention counts.
How Arize compares
Pulse Score over the selected period versus the top tracked competitors in Coding.
Where the mentions come from
Share of the 178 relevant public mentions in the selected period, by source.
Sample public mentions
Showing 5 of 178 analyzed public mentions in this period, with links to the original source. We do not reproduce full threads.
“[BUG]:No module named 'phoenix.evals.models'. ### Where do you use Phoenix Self-hosted What version of Phoenix are you using? _No response_ What happened? Additional information Name: arize-phoenix Version: 4.35.0 --- Name: arize-phoenix-evals Version: 3.0.0 --- Name: arize-phoen...”
“[bug] error importing PipecatInstrumentor due to deprecations in pipecat v1.0.0. **Describe the bug** Pipecat has released their v1.0.0 which had a lot of deprecations and files removed. One such removal is throwing the following error when trying to import PipecatInstrumentor: M...”
“[BUG] crypto.randomUUID is not a function. I installed the latest version of arize-phoenix. I turned on both feature flags agents and tracing_ux. After turning them on I see: I turn them off and I can navigate phoenix again but when I access any trace I see the screen again.”
“[feature request] add support for model name for nova models. ## Is your feature request related to a problem? Please describe. The Python Bedrock auto-instrumentation (openinference-instrumentation-bedrock) does not support Amazon Nova Sonic 1 or Nova Sonic 2 models. When using ...”
“[ENHANCEMENT]: resume_experiment ignores stored splits and lacks a dry_run parameter. ### Is your feature request related to a problem? Please describe. Note: this issue is mostly about resume_experiment missing the same expected functionality as run_experiment so apologies if th...”
908+ more analyzed mentions, full history, and theme breakdowns are part of Pro.
Get ProDeeper analysis
- Bug reports and reliability complaints dominated discussion and far outnumbered positive mentions across the four-week window.
- Sentiment followed a volatile trajectory, briefly recovering in late May before retreating again in early June and remaining soft into late June.
- Opinion was divided on competitor comparisons, with some commenters citing Arize favorably and others using the same frame to express dissatisfaction.
- Documentation gaps and missing privacy controls drew secondary frustration from a subset of commenters beyond the core stability concerns.
| Praise theme | Mentions |
|---|---|
| Strong features | 33 |
| Good integrations | 31 |
| Feature requests | 6 |
| New releases | 5 |
| Polished UI | 4 |
| Complaint theme | Mentions |
|---|---|
| Bugs | 84 |
| Reliability | 58 |
| Missing features | 24 |
| Compared to rivals | 12 |
| UI frustrations | 11 |
Discussion of Arize across the four-week window carried a persistently negative tone, with bugs and reliability concerns dominating the conversation by a wide margin. Of the 61 total mentions captured, complaints around bugs accounted for 26 and reliability issues for 17, meaning instability-related frustration represented the clearest and most consistent thread commenters returned to. Sample mentions reinforced this tone directly, with several bug reports detailing specific instrumentation failures, including span output being overwritten, token count mapping errors inflating cost calculations, and tool metadata being silently dropped during processing. These were not vague gripes but pointed technical grievances, suggesting an engaged but increasingly frustrated user segment.
The score trajectory tells a story of volatility with a broadly soft trend. Sentiment opened the window in weak territory in early May, dipped further in mid-May when mention volume peaked at 23, then recovered modestly toward late May before sliding back sharply in early June. The window closed with scores in the mid-forties, which commenters-adjacent signals suggest may be fragile given the renewed bug discussion volume in mid-June. No extended upward run materialized across the period.
Praise was present but narrower in scope. Feature praise and integration satisfaction drew the most positive mentions, and a small cluster of competitor comparison entries appeared on both the praise and complaint sides, indicating divided opinion on how Arize stacks up against alternatives. Some commenters framed the product favorably in that context while others used the same frame critically.
Missing features and feature requests added a secondary layer of dissatisfaction, with one mention highlighting a gap in privacy controls for user-generated content. Documentation quality also surfaced as a concern, with an audit mention flagging actionable gaps and a specific complaint about duplicated or scattered documentation across surfaces. These themes occupied less space than the bug cluster but contributed to an overall sense that the product experience felt unpolished to a portion of its users.
AI-generated summary of public online discussion during this period. It reflects the tone of that discussion, not facts about the product or our views.
Member perspectives
Individual opinions from Pro members, posted over time. These are personal member views, not aggregated sentiment data.
Overall Pulse Score
-2 over this period
A 0-100 index summarizing the tone of 178 relevant public mentions gathered from public online communities across 12 weeks in the selected period. It measures online sentiment, not a rating of the product's quality.
Data summary
Compare with another tool
Arize
40
Trainual
88
Score-level preview from live weekly tracking.
Are you Arize?
If you represent this product, you can share context about the data shown here. We read every submission.
Share feedbackAffiliate disclosure
Some links on this site may be affiliate links. If you click one and make a purchase, we may earn a commission at no extra cost to you. Learn more.
Compare with similar tools
RevenueCat
A platform that manages in-app purchases, subscriptions, and revenue analytics for iOS and Android app developers.
Free tier; paid plans available
View DetailsCodemirror
An open-source JavaScript code editor component for browsers, used by developers building web-based text and code editing interfaces.
Free
View Details