bgpreport

Network · data from 2026-11-12

AS396893 mitelefono.com

Registry name: WWMS - mitelefono.com, US · PeeringDB

2IPv4 routes 100.0% RPKI valid · 50.0% with a route object
2IPv6 routes 100.0% RPKI valid · 50.0% with a route object
0RPKI invalid 0 origin · 0 maxLength
0No ROA 2 with no route object for this origin
0Low visibility seen by under 10% of full-table peers
0Route objects not announced registered with origin AS396893, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS396893, things to look at first. Visibility = full-table peers that see it, of 673 (IPv4) and 636 (IPv6) on 75 collectors. Also as routes.csv.
23.132.232.0/24 Valid Other origin only 673 100% 67
2620:8d:a000::/48 Valid Other origin only 634 100% 67
23.132.82.0/24 Valid RIR databaseARIN 671 100% 67
2606:b440::/32 Valid RIR databaseARIN 635 100% 67

AS-SET

AS396893's PeeringDB record names no AS-SET.

Fix list

The changes that would bring RPKI, the IRR and what's announced into line. Some are deliberate (a route object kept for a backup route, say); the network decides. All 2 are in fix.csv.

  • Route object: none2
ChangePrefix or setDetailFull-table peers
Route object: none23.132.232.0/24Route objects for it name AS40153. Add a route object with origin AS396893 in the RIR database for the space.673 of 673
Route object: none2620:8d:a000::/48Route objects for it name AS40153. Add a route object with origin AS396893 in the RIR database for the space.634 of 636

Route objects not announced

Every route object with origin AS396893 is announced.

Routes: the 08:00 UTC snapshots of 2026-11-12 from 75 RIPE RIS and RouteViews collectors. RPKI: our rpki-client run before the snapshot. IRR: the day's dumps of the five RIR databases and RADB's mirrors. The LEVEL3 and IDNIC databases publish no dump and aren't read, so route objects only there count as none.