pagination interpreted as offset?

We've noticed a change in the API response since the introduction of pagination.
When requesting the configured services (using /ecx/v3/l2/buyer/connections?pageNumber={page}&pageSize=1) we receive the same service multiple times. When we move to a next page the advance the pointer to the next record which makes us believe this is actually the "offset".
So pageNumber points to the n-th record and pageSize determines how many they return, this means that size=100 on page 1 (start from 0) you get only 1 new record and 99 old ones.
ex. if you want record 100, with page size 100, you don't need page 1, you need page 100.

I'm guessing this counts as a bug in the API, no?