What is your miner? Claymore doesn’t want to accept this address for either solo-coin or autoswitch-algo

Thanks! EDIT: It worked!!! Thanks again!
And since I didn’t believe it is miningpoolhubstats.com fault, looks like I raised the question in the right place

Is it me? There is no Worker Stats on miningpoolhubstats.com
But then again, I cannot see my hashrate on MPH itself for the second day (could be longer,but it is only second day I use Algo-Switch; before was a single-coin mining, which was showing the hashrate more or less aaccurate)

Thanks! Trying it out now.
(No log in link takes to 404 page LOL). Well, will be one more login to store.

As to MPH’s Balances page - VERY delayed info (IMHO that is anyway)...

Can someone, please, tell me WHAT do I mine?
Not asking for an advice. The status.
The miner is working, hub worker configured; no balances though at the moment and the hash rate on the pool, which is marked as selected in stats and auto switches, shows 0...
Is there a way TO SEE that all the hashing DOES GO somewhere and COUNTS?

EDIT:
What I mean: it is an auto-switching pool(s). There shall be a single place (a statistic page/table) clearly showing that the job done, the submitted shares (marked in my miner as Accepted) do count towards something (and what exactly that something is at this moment/round).
I can monitor a pool worker but not the hubworker! And that is the one actually working when you go for the main feature of this pool(s), the auto-switching!..

16437 ms!
WOW!!!

Definitely hope so. I just posted on another error I got today. Might be related, for all I know

I wanted to try today MultiPoolMiner but got not-described error: "Index was out of range. Must be non-negative and less than the size of the collection". Waiting on Github for a possible solution...
So, I tried Multi-algo switch mining (Port 12XXX) different algo coins by using Hub feature,via the hub worker -- Claymore miner @ us-east-equihash-hub.miningpoolhub.com:12023 (SSL/TLS)
and after some time the miner would give first:
"...
Stratum -- reading socket failed 0, disconnect
ZEC: Connection lost, retry in 20 sec...
..."
then, the attempt to connect with the message "ZEC: Stratum -- Connected"
and then
"...
ZEC: Authorization failed
: {"id":2."result":false,"error":null}
..."
Happened few times today. Before, I was mining non-stop BTG (port 20595) for 10 days without a single error (and only 7 rejected shares). So, I am afraid to leave this switching miner on for the night; went back to a single-coin (btg).

Is it me? Or the servers' updates did do some bad service?..

Nope, not only you.
I had steady 43ms for the past two weeks. Left for 4 days; now back and have acceptance times in 2-5-hundreds ms also.
That is on US-East @ BTG and Equihash servers. And I think, Intel patch announcement came later than this happened/changed