bgpreport

Network · data from 2026-11-12

AS28400 AS28400 - SECRETARIA DE INFRAESTRUCTURA, COMUNICACIONES Y TRANSPORTES DIRECCION GENERAL DE TECNOLOGIAS DE INFORMACION Y COMUNICACIONES

Registry name: AS28400 - SECRETARIA DE INFRAESTRUCTURA, COMUNICACIONES Y TRANSPORTES DIRECCION GENERAL DE TECNOLOGIAS DE INFORMACION Y COMUNICACIONES, MX · not in PeeringDB

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

Announced routes

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

2806:330:2064::/48 No ROA Other origin onlycovered by 2806:330::/32 634 100% 68

AS-SET

AS28400 isn't in PeeringDB, where networks name their 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 4 are in fix.csv.

  • ROA: none1
  • Route object: none1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
ROA: none2806:330:2064::/48No ROA covers it. Add a ROA for AS28400, maxLength 48.634 of 636
Route object: none2806:330:2064::/48Route objects for it name AS8151. A route object for 2806:330::/32 with origin AS28400 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28400 in the RIR database for the space.634 of 636

Route objects not announced

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

177.234.0.0/17RADBNo ROA
2806:330::/32RADBNo ROA

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.