Does the back-end do something odd with integer based pool names? Just a though but probably not as 000 and 00000 yield results.
Updated the pools metadata a couple weeks back (including ticker change) . But these changes should now be reflected. Is the DB source invalid or infrequent checks (...or never updated once a ticker is found)?
To Reproduce Steps to reproduce the behavior:
Expected behavior Expect to see stake pool with ticker 9000 (https://cexplorer.io/pool/pool1fu6ppur5uumrpydpeswzrvfg4epr68xw39aar9rcu56tk5ukat3)
Additional context / Considerations
Thanks, Jack