
New Member
•
5 Messages
My phone usage logs are reflecting incoming numbers from my number.
When I pull my phone records my text messages and calls reflect my number as if I am texting/calling myself. I understand if I block a number it will reflect my number in its place, but I am also experiencing if someone calls and texts from their number or an App number that I do not have blocked it also reflects my number as I'm calling or texting myself. My device clearly shows someone's personal number coming through but my logs reflect my number. Is this a glitch in the system and why does this happen? Point being if I am being harassed and go make a police report I can not pull my phone records to prove anything because it looks as if I'm making it all up since it reflects my personal number. An actual number comes through on my device but records of my usage data reflect my number. I'm seeing this is a huge issue for a lot of people!
ATTHelp
Community Support
•
225.4K Messages
2 years ago
Hello @Anecessary1106, we want to look further into why your data logs aren't reflecting other phone numbers.
First, you'll need to confirm with us which way you're checking your data usage. Also, please review the following options for checking your usage:
Feel free to reach back out and let us know how this helped and confirm with us which way you're checking your usage.
Thanks for reaching out to the AT&T Community!
Lynn, AT&T Community Specialist
0
0
Anecessary1106
New Member
•
5 Messages
2 years ago
So maybe I used the incorrect terminology. I am checking my log history for text and calling online and it is showing my number for all my incoming texts.
0
0
ATTHelp
Community Support
•
225.4K Messages
2 years ago
Let's figure out what's causing the error in your usage details, @Anecessary1106.
We update your usage reports as quickly as we can, but sometimes your usage info may be unavailable or delayed under certain circumstances.
If you're viewing your usage through the myAT&T app, we'd like to suggest you try some basic app troubleshooting:
If you're logged on through a web browser, we recommend clearing your cache and cookies or all of the open tabs for a better browsing experience.
After you've tried all the troubleshooting options provided, please try viewing your usage details again to see if you experience the same mishap.
Thanks for reaching out to our AT&T Community! We look forward to helping you through this.
Sydne, AT&T Community Specialist
0
0
Anecessary1106
New Member
•
5 Messages
2 years ago
I have done all of these things. This has been happening for years. This time all my incoming texts are my number showing. According to this forum if a blocked number or App number text or calls and I reply back ATT is not able to trace the number so its replaced with mine showing me texting/calling myself. That's a major glitch! I'm seeing folks divorce and lose significant others behind this due to not being able to prove who is calling or texting.
0
0
shellbell1974
New Member
•
1 Message
2 years ago
This is happening to me as well.
Or I get the following error; Error code: USAGEORCHESTRATOR_WLSACTMS_ACCOUNT_DETAILS__NULL_BILLCYCLE
This has been happening for a month. I have tried everything. Any solutions?
0
0
Anecessary1106
New Member
•
5 Messages
2 years ago
Hopefully they can help you...I've never received any error codes I just have issues with my incoming and outgoing text/calls reflecting my number making it look like im talking to myself.
0
0
ATTHelp
Community Support
•
225.4K Messages
2 years ago
Thanks for meeting us back here with that update, @Anecessary1106.
We've noticed the trend, and we're looking into this further. Thanks for reaching out to our AT&T Community!
Sydne, AT&T Community Specialist.
0
0
Anecessary1106
New Member
•
5 Messages
2 years ago
Thanks for the response but this is more than a trend. This has been an issue with thousands of folks for years. I dont know how ATT has not came up with an answer or claim they never heard of it when this has been an ongoing issue.
0
Rawwdacious
New Member
•
1 Message
8 months ago
Has this been resolved?
0
0