HTTP 206 Did Not Tell Us How Much Video We Were Still Reading
We measured storage reads after a client abandoned a range, checked exact bytes and kept the real browser-pause gap separate from the curl test.
Reviewed by Dmytro Nasyrov on October 27, 2026.
An HTTP 206 response can look correct while the storage client keeps reading the rest of a video after the viewer has moved elsewhere. We tested our authenticated media path by checking the bytes read from object storage, not only the headers returned to the caller.
Our learning product served cited media through a backend and a chat-side relay. A reader needed authorization, a correct byte range and a way to stop consuming the old range when seeking. Those requirements crossed more than one connection.
Start with a file whose bytes can be compared
The recorded test used a synthetic 19,586,841-byte video. Both routes were checked against the local file, so an offset error could not hide behind a playable-looking clip. A closed range returned the expected 100,000 bytes. A suffix request returned the final 65,536 bytes. An out-of-bounds range returned 416 with the total length and no body.
A request without a range returned the complete file with the recorded SHA-256 match.
Without a session, the chat route returned 401.
These were separate controls: correct range arithmetic did not establish the access boundary, and an access check did not establish the content.
Read a little, then leave
For open-ended ranges, each caller read 300,000 bytes and disconnected. The backend recorded how many bytes its storage stream had consumed before aborting. A clean cancellation need not mean exactly 300,000 upstream bytes: buffers and read-ahead can account for more. It should prevent the remaining file from being drained without a reader.
| Requested start | Caller read | Chat storage read in the recorded check |
|---|---|---|
| 0 | 300,000 bytes | 364,344 bytes |
| 3,000,000 | 300,000 bytes | 356,128 bytes |
| 8,000,000 | 300,000 bytes | 536,064 bytes |
| 13,000,000 | 300,000 bytes | 553,488 bytes |
| 18,500,000 | 300,000 bytes | 456,288 bytes |
Across the five seeks on each route, storage reads totaled about 2.28 MB for the demo path and 2.27 MB for chat. Reading each requested range to its end would have consumed 55.4 MB. This was a transport comparison on a synthetic file, not a bandwidth saving forecast for real viewers. The evidence joined a ranged object-store request, an aborted storage read and a client-left event. Counting outgoing backend bytes alone would not establish how much the storage SDK had already pulled. Conversely, a request header alone would not prove that closing the downstream path canceled the upstream stream.
Pause and abandon are different experiments
A second check emulated a stalled reader with curl. It accepted the headers and then read no body bytes for 150 seconds. The backend initially filled transport buffers, then stopped progressing. About a minute after its writes stopped, it gave up the transfer and recorded an aborted storage read.
The transport had already buffered substantial data. The recorded storage read reached 14,794,752 bytes out of the 19,586,841-byte file. That observation prevents an overly strong claim that backpressure instantly stopped all upstream reads. It also shows why a pause experiment needs buffer and timeout context.
A new request from the middle then returned 206, and the next 300,000 bytes matched the local file at that offset. This established a resumed request after an abandoned connection. It was not the same browser player preserving and resuming its original connection.
authenticated request
-> parse one supported range
-> ranged storage read
-> downstream response
-> downstream closes
-> abort upstream read, record bytes consumedThe surprising cost of asking only for headers
The record also found a separate inefficiency in the chat relay: it exported GET but no dedicated HEAD handler. In that pinned application, a HEAD request ran the GET path. The backend read 4,831,496 bytes from storage before the relay let go, despite the caller asking for no response body.
Video players in the checked path sought using ranged GETs, so the observation did not invalidate the seek results. It did invalidate the broader statement that every metadata request was cheap. A future HEAD regression should inspect storage consumption as well as the absence of a downstream body.
Keep the browser gap visible
The implementation notes explicitly left a real browser pause of at least two minutes for the developer to check on staging. We cannot turn the curl emulation into that missing acceptance result. Player buffering, browser retries and the deployed proxy chain can change the user-visible behavior.
The case supports a bounded protocol claim: the recorded media paths returned correct range bytes and stopped old object-store reads after downstream departure. It does not establish every player's behavior, a universal cancellation latency or a service-level bandwidth guarantee. For another media proxy, the inspectable artifact is a joined record of requested offset, returned byte comparison and upstream bytes consumed after departure. Keep the full-file and unauthorized controls beside it; neither can be inferred from a successful seek.
FAQ
Quick answers to common questions about custom software development, pricing, process and technology.
Type to filter questions and answers. Use Topic to narrow the list.
Showing all 14
No matches
Try a different keyword, change the topic or clear filters
-
How long have you been in business?
Pharos Production has been in business since 2013, with over 13 years of experience in custom software development. During this time, we have delivered over 110 applications for 200+ clients across 28 industries, including FinTech, healthcare, crypto and e-commerce. We are rated 5/5 on Clutch based on 107 verified reviews (2026).
-
What services do you provide?
Pharos Production provides six core service categories: AI Development (LLM applications, AI agents, machine learning and computer vision), Blockchain and Web3 (smart contracts, DeFi, tokenization on Ethereum, Solana, TON and other chains), FinTech Development (payment platforms, digital banking, KYC and AML integration), Software Development (mobile apps, web platforms, database design, UI/UX), Security and QA (code audits, penetration testing, smart contract audits, manual and automated testing) and Consulting (architecture design, MVP validation, startup consulting).
-
Where is Pharos Production located?
Pharos Production is headquartered in Las Vegas, Nevada, USA (5348 Vegas Dr, Las Vegas, NV 89108), with an engineering office in Kyiv, Ukraine (44-B Eugene Konovalets Str. Suite 201, Kyiv 01133). We work with clients worldwide and provide remote collaboration across all time zones. Visit our contact page for directions and scheduling options.
-
How big is your team?
Pharos Production has a team of 90+ engineers, including software developers, blockchain specialists, QA engineers, DevOps experts, UI/UX designers, project managers and solution architects. Our founder, Dr. Dmytro Nasyrov, holds a PhD in Artificial Intelligence and leads the technical direction of all projects.
-
What types of customers do you serve?
We serve a wide range of clients, from startups and product companies to mid-sized enterprises and large institutions. Our clients include crypto exchanges, FinTech providers (like Pleenk), healthcare organizations, sportsbook operators (like Pro Gambling), e-commerce platforms and SaaS companies. Pharos Production has worked with 200+ clients across 28 industries since 2013, adapting engagement models to match each client's stage, whether it is MVP validation for a startup or enterprise-scale development for an established business.
-
How is a custom software development company different from an agency?
A custom software development company like Pharos Production assigns one dedicated engineering team that owns your product across multiple release cycles, instead of handing it off once a contract ends. Agencies more often rotate staff between clients and optimize for fast delivery over long-term product ownership.
Pharos Production keeps the same team on your codebase through 2-week sprints, so there is no re-onboarding cost each time you request a new feature.
-
How much does custom software development cost?
Custom software development costs vary based on project scope and complexity. At Pharos Production, typical project ranges are: MVP development ($10,000-$25,000), suitable for startups validating a product idea; full-fledged production ($25,000-$50,000), for established businesses scaling a proven concept; and full-cycle development ($50,000-$80,000+), for complex enterprise-grade systems. These ranges include architecture design, development, QA testing and deployment. Hourly rates range from $50 to $99 depending on role and seniority. Final pricing depends on technology stack, number of integrations and engagement model (staff augmentation, dedicated team or project outsourcing).
-
How long does it take to develop a custom software application?
Development timelines depend on scope and complexity. At Pharos Production, a typical MVP takes 2-4 months, a production-ready application takes 4-8 months and a complex enterprise system can take 8-12+ months. We use an agile methodology with 2-week sprints, delivering working increments after each sprint. Every sprint includes a retrospective, progress report and planning session for the next iteration. This approach ensures transparency and allows businesses to launch faster by prioritizing high-impact features first. Get a timeline estimate for your project.
-
What industries does Pharos Production serve?
Pharos Production serves 28 industries: FinTech, MiCA Compliance, Banking, Insurance, Crypto, Healthcare, Fitness, E-Commerce, Food & Restaurant, On-Demand, Manufacturing, Automotive, Energy, Oil & Gas, Supply Chain, Construction, Real Estate, Gaming, Streaming, Media, Telecom, Education, Aviation, Travel, Logistics, Marketing, Agriculture and Recommender Systems. Our deepest expertise is in FinTech, blockchain and healthcare, where we have delivered compliance-ready platforms (HIPAA, PCI DSS, GDPR) and high-load systems handling thousands of concurrent users. For the latest industry insights, read our guides on FinTech trends in 2026 and the Web3 technology stack.
-
Why hire a software development company instead of building in-house?
Hiring a software development company offers faster time-to-market, lower upfront costs and access to specialized expertise without long-term employment commitments. According to Deloitte's 2024 Global Outsourcing Survey, 57% of companies outsource software development to access skills they cannot hire internally.
Factor In-house team Software development company Time to assemble 3-6 months (recruiting + onboarding) 1-2 weeks Upfront cost High (salaries, benefits, equipment) Lower (project-based pricing) Specialized expertise Limited to who you can hire locally Access to 90+ engineers across blockchain, AI, FinTech Scalability Slow (each new hire takes months) Fast (scale up or down per sprint) Long-term commitment Full-time employment contracts Flexible engagement models Risk High if key engineers leave Company ensures continuity and knowledge transfer For businesses that need blockchain, AI or high-load architecture expertise, outsourcing to a specialized firm like Pharos Production reduces risk and accelerates delivery.
-
What projects does Pharos Production not take on?
Pharos Production focuses on mid-to-large custom software projects with budgets starting at $10,000. We do not take on template-based websites, WordPress theme customization or short-term contracts under one month. We also do not provide non-technical staffing (marketing, sales or design-only roles). Our strongest fit is blockchain, FinTech and healthcare projects where security, compliance and high-load architecture are critical. For smaller projects or MVPs under $10,000, we recommend exploring freelance platforms or no-code tools as a more cost-effective starting point.
-
Why does Pharos Production use agile methodology?
We use agile with 2-week sprints because it reduces the risk of building features that miss the mark. Each sprint ends with a working demo, a retrospective and a plan for the next iteration.
This means clients see progress every 14 days and can adjust priorities based on real results, not assumptions. We chose this approach after years of experience showing that rigid, fixed-scope contracts lead to scope creep, missed deadlines and products that do not match market needs by launch day.
-
When should you NOT hire a custom software development company?
Custom development is not the right choice in every situation. You should not hire a custom software company if: your problem is fully solved by an existing SaaS product (e.g. Shopify for e-commerce, Salesforce for CRM); your budget is under $10,000 and timeline is under 4 weeks; you need a simple landing page or marketing website (WordPress or Webflow is faster and cheaper); or you are still validating the idea and have not spoken to potential users yet.
In these cases, off-the-shelf tools or no-code platforms offer better ROI. Custom development makes sense when you need unique workflows, regulatory compliance, high-load architecture or competitive differentiation that packaged software cannot provide.
-
What kind of projects has Pharos Production delivered?
Here are three anonymized examples from our recent delivery history:
FinTech startup - payment platform (MVP)
Scope: mobile app + backend API with bank-grade encryption. Team: 4 engineers, 1 QA. Timeline: 10 weeks. Budget: $38,000. Result: launched on schedule, processed $2M+ in transactions within the first quarter.Healthcare provider - patient portal (Full product)
Scope: HIPAA-aligned web platform with EHR integration, appointment scheduling and telemedicine. Team: 6 engineers, 1 DevOps, 2 QA. Timeline: 6 months. Budget: $120,000. Result: 15,000+ active patients, zero compliance violations in two annual audits.Crypto exchange - trading engine (Complex)
Scope: high-load matching engine handling 50,000+ orders per second, multi-chain wallet infrastructure on Ethereum and Solana. Team: 8 engineers, 2 QA, 1 security auditor. Timeline: 11 months. Budget: $340,000. Result: 99.97% uptime, passed three independent security audits.See more projects: NoMoreBets, Pulse, Sagas, Gambit Stream and Pleenk. For the full portfolio, visit our case studies. Learn more about the technology behind these projects in our guide to stablecoins and crypto infrastructure.
Dmytro Ihnatov is the Lead Backend Developer at Pharos Production. He documents backend architecture and research experiments from the team's work on a professional learning platform for aesthetic medicine.
