The short answer
The registry records Fly.io Edge MicroVM Compute & Persistent Storage as a possible interpretation of FLY.IO* MACHINES. This descriptor-to-company association has not passed claim-level evidence review. Compare the exact line, amount and posted status with your own receipt or account activity; the name alone cannot confirm the merchant or whether you authorized the payment.
What do the parts of FLY.IO* MACHINES mean?
- FLY.IO * MACHINES
- Before the asterisk, "FLY.IO" usually names the platform or parent company. After it, "MACHINES" usually names the product, store or order. How descriptors work →
- FLY.IO
- A web address in the line. Compare it with the company site on your receipt or account email before relying on it.
The notes below are unreviewed registry explanations, not confirmation of merchant identity, authorization or current policy. Claim-level source review is pending for this entry.
Why it shows up like this
Unreviewed registry note: A line item on your bank statement reading FLY.IO* MACHINES is an infrastructure compute charge from Fly.io, Inc. Fly Machines are lightweight Firecracker microVMs that boot in fractions of a second to run backend applications, background worker queues, or serverless functions close to users worldwide. Invoices appear under descriptors like FLY.IO* MACHINES, FLY.IO, FLY CHICAGO, or FLY.IO INC, representing metered hardware consumption for Fly.io Edge MicroVM Compute & Persistent Storage across global data center regions.
Unreviewed registry note: This charge appears because your organization ran microVM instances or provisioned persistent storage disks that accrued metered billing during the preceding monthly cycle. Similar to cloud application platforms like Railway or standard Fly.io cloud hosting, billing is calculated per second of CPU and RAM execution, alongside fixed monthly storage fees for NVMe persistent volumes. Machines configured with auto-start triggers can wake up in response to incoming HTTP traffic across multiple regions, resulting in unexpected usage if traffic continues or health checks keep instances active.
Don’t recognize it? Common scenarios
Unreviewed registry note: Teams frequently configure Fly Machines to wake on incoming network traffic, which can keep instances active longer than anticipated if automated bots or health monitors probe the service. Even when machines are stopped, attached NVMe persistent volumes continue to bill for disk capacity.
- Unreviewed registry note: A Fly Machine auto-started in response to incoming HTTP traffic and stayed running across multiple edge regions.
- Unreviewed registry note: An allocated Fly NVMe persistent volume was retained on an inactive or stopped machine.
- Unreviewed registry note: Dedicated IPv4 addresses ($2/mo each) remained assigned to an organization.
Frequently Asked Questions
Why was I charged for a stopped Fly Machine?
Unreviewed registry note: While stopped microVMs do not incur compute CPU charges, attached NVMe persistent storage disks and dedicated IPv4 addresses incur monthly retention fees.
Dispute Rights & Fraud Prevention
Unreviewed registry note: Verify with your technical staff or contractors whether someone created a microVM workspace for testing or production deployment. If you find unauthorized charges or suspicious account activity, submit a support ticket via community.fly.io and notify your financial institution to protect your card.
Independent reference — not affiliated with Fly.io, Inc.. Billing names and policies change; verify with the merchant or your bank before acting.
Sources and evidence
Sources may support different parts of this page. A company homepage does not establish a statement descriptor, refund policy or contact detail. Check the claim notes and your own receipt before acting.
- Fly.io Pricing & Machine Billing Documentation https://fly.io
- CFPB: Disputing Unrecognized Charges https://www.consumerfinance.gov
Evidence review pending · pending · About UnknownCharges