Tag Archives: TibiaData

TibiaData release v4.2.3

We have released a new version of TibiaData!

Changed

You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md

You can find the v4.2.3 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.3

Kind regards,
Tobias

Ongoing disturbances in our API

We had some disturbances regarding the API due to networking issues in our Hetzner Cloud Kubernetes cluster in Nuremberg, where our Kong gateway stopped working due to our autoscaler.
Symptoms where both 503 responses and no traffic from our Load Balancer towards the service.

Complete service outage with 503 error responses:
Start: 2024-08-01 01:48
Stop: 2024-08-01 06:46

Kind regards,
Tobias

TibiaData release v4.2.2

We have released a new version of TibiaData!

Fixed

You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md

You can find the v4.2.2 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.2

Kind regards,
Tobias

TibiaData release v4.2.1

We have released a new version of TibiaData!

Fixed

You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md

You can find the v4.2.1 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.1

Kind regards,
Tobias

TibiaData restriction-mode

We don’t like limiting our service and do consider fair and reasonable as the best way for all of us.
We don’t like users that are trying to walk around our caching in our API gateway, not respect certain error-responses or exorbitant hammering of certain endpoints.

But sometimes things happen that shouldn’t, which then leads to the collective of tibiadata-users to suffering as of the release with v4.2.0.

What happened?

Due to some heavy use of the highscores endpoint (around 150.000 requests on a 10 minutes period), the creators of Tibia have asked us to implement limitations.

The changed behaviour did create an increase of traffic over 100% and due to the short period of time, it created issues on their side.

What endpoints are effected?

Currently the restriction-mode is only enabled on the highscore-endpoints, which were subject to the large change in request behaviour.

You can still use the highscore-endpoint itself, but you the option to use the vocation filtering is removed and you can only use all as filter.

Will this be permanent?

Not sure about that yet, but hopefully not. We are still in communication with CipSoft about this.

Still want some filtered highscores?

Contact us (preferably on Discord) if you have some low amount of highscore-requests and we can try to figure out a way forward.

Kind regards,
Tobias

TibiaData release v4.2.0

We have released a new version of TibiaData!

Added

Changed

Fixed

You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md

You can find the v4.2.0 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.2.0

Kind regards,
Tobias

Ongoing disturbances in our API

We had some disturbances regarding the API due to networking issues in our Hetzner Cloud Kubernetes worker in Nuremberg.
Symptoms where both 503 responses and temporarily no traffic from our Load Balancer towards the service.

Intermittent connection issues and 503 error responses:
Start: 2024-04-05 05:15
Stop: 2024-04-06 10:47

Complete service outage due to restarts:
Start: 2024-04-06 10:47
Stop: 2024-04-06 10:58

Kind regards,
Tobias

TibiaData release v4.1.2

We have released a new version of TibiaData!

Changed

Fixed

  • character killer parser by rewrite of death parsing logic (#338 by phenpessoa)

You can find the changes in our Changelog
https://github.com/TibiaData/tibiadata-api-go/blob/main/CHANGELOG.md

You can find the v4.1.2 release on GitHub on
https://github.com/TibiaData/tibiadata-api-go/releases/tag/v4.1.2

Kind regards,
Tobias

Maintenance of our service due to migration

Today it’s finally time for a maintenance of our service due to a migration of our hosting provider.

We are moving after being hosted at DigitalOcean since 2016 to Hetzner Cloud.

For those that are more interested into the technical details, here they are:

  • K3s Kubernetes cluster spanning over multiple datacenters
  • ArgoCD is deploying and updating our components in the cluster
  • Kong Gateway Operator is managing our Kong API Gateway
  • DNS has been migrated to Hetzner DNS service
  • TLS termination is handled by Hetzner Load Balancer
  • IPv6 is now available on our service

If you have issues, please contact us on our Discord server or some alternative mentioned on our Contact us page.

Kind regards,
Tobias