bgpreport

Network · data from 2026-11-12

AS396313 MocTel inc.

Registry name: MOCTEL - MocTel, CA · PeeringDB

6IPv4 routes 100.0% RPKI valid · 100.0% with a route object
2IPv6 routes 100.0% RPKI valid · 0.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
10Route objects not announced registered with origin AS396313, seen from no peer

Announced routes

Every prefix a peer of the route collectors sees with origin AS396313, 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.

2602:fef2:3::/48 Valid Nonecovered by 2602:fef2::/36 604 95% 67
2602:fef2:113::/48 Valid Nonecovered by 2602:fef2::/36 604 95% 67
23.171.128.0/24 Valid RIR databaseARIN 673 100% 67
199.250.63.0/24 Valid RIR databaseARIN 673 100% 67
199.250.62.0/24 Valid RIR databaseARIN 670 100% 67
199.250.60.0/24 Valid RIR databaseARIN 668 99% 67
199.250.61.0/24 Valid RIR databaseARIN 668 99% 67
74.49.154.0/24 Valid RIR databaseARIN 665 99% 67

AS-SET

AS396313'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 12 are in fix.csv.

  • Route object: none2
  • Route object: not announced10
ChangePrefix or setDetailFull-table peers
Route object: none2602:fef2:3::/48No route object for it. A route object for 2602:fef2::/36 with origin AS396313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396313 in the RIR database for the space.604 of 636
Route object: none2602:fef2:113::/48No route object for it. A route object for 2602:fef2::/36 with origin AS396313 covers it (filters allowing more-specifics accept it). Add a route object with origin AS396313 in the RIR database for the space.604 of 636

Route objects not announced

Route objects with origin AS396313 whose prefix no peer sees AS396313 announce. Many are kept on purpose (backup routes, space announced only in some places).

23.134.32.0/24ARINValid
23.178.0.0/24ARINValid
23.178.1.0/24ARINValid
23.252.224.0/20ARINValid
64.235.196.0/24RADBNo ROA
199.4.190.0/24ARINValid
199.250.60.0/22ARINValid
2602:fef2::/36ARINValid
2604:d040::/32ARINValid
2606:7480::/32ARINValid

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.