API status

All systems up

API (api.lynxmetrics.com)RespondingChecked at

Table in play: rounds are coming out normally.

Last round at 104 rounds in the last hour2,305 in the last 24 hours

Time with rounds coming out

96.08%last 24 hours

24 hours agonow

97.72%last 7 days

7 days agonow

Rounds coming outShort stopLong stop

2 readers on this table

  • Reader 1Reading

    table video

    • Checks every round and takes over on its own if the other stops
    • Last reading at
    • 2 of 2 video servers up
  • Reader 2Reading

    game state

    • Rounds go out through it
    • Last reading at

Stops in the last 24 hours

  • – 3 minslow round at the table
  • – 2 minunstable table video
  • – 6 mintable stopped (provider pause)
  • – 9 minunstable table video
  • – 2 minno recorded cause
  • – 2 minno recorded cause

Lightning Baccarat

Reading paused

Reading of this table is paused on purpose; it is not a failure. The API answers with the rounds it already has.

Last round at

1 reader on this table

  • Reader 1Off

    table video

    Table in play: rounds are coming out normally.

    Last round at 119 rounds in the last hour2,779 in the last 24 hours

    Time with rounds coming out

    99.35%last 24 hours

    24 hours agonow

    97.23%last 7 days

    7 days agonow

    Rounds coming outShort stopLong stop

    1 reader on this table

    • Reader 1Reading

      table screen

      • Rounds go out through it
      • Last reading at

    Stops in the last 24 hours

    • – 4 minno recorded cause
    • – 3 minno recorded cause
    • – 3 minno recorded cause

    Each table is read by one or more independent readers. With more than one, a round goes out through whichever delivers it first, the others check it, and if one stops the other carries on alone: the same round never goes out twice.

    A table with no new rounds is usually a pause at the provider (dealer change, shuffle or maintenance), not an API failure: in that case the API keeps answering with the last round. This page refreshes on its own.

    Your bot stopped and everything here is up? See what breaks bots most often or talk to support.

    Frequently asked questions

    Is the API down, or is it my bot?
    If this page shows everything up and your bot stopped, the problem is on your side: the key, the plan limit or a network error. The documentation lists the error codes and what each one means.
    What does “no new rounds” mean?
    That the table has not delivered a round for longer than usual. It is almost always a pause at the provider (dealer change, shuffle or maintenance), and the page says when that is the case: the readers show as up and the table as stopped. The API keeps answering with the last round it got.
    What are the readers?
    They are the paths through which we read each table. Bac Bo has two independent ones: one reads the table video and the other reads the game state. A round goes out through whichever arrives first, the other checks it, and if one stops the API carries on through the other.
    How often does this page refresh?
    It refreshes on its own every minute, and the reading is redone on the server every 30 seconds. There is no need to reload.
    Can my bot check the status on its own?
    It can: https://api.lynxmetrics.com/health answers in JSON, with no key, and says whether the API is up and the collectors are running.