bgpreport

Network · data from 2026-11-19

AS275559 AS275559 - MGA37

Registry name: AS275559 - MGA37, MX · not in PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS275559, things to look at first. Visibility = full-table peers that see it, of 672 (IPv4) and 633 (IPv6) on 75 collectors. Also as routes.csv.

2806:20d:2d3a::/48 Invalid: origin None 39 6%low visibility 26
38.22.178.0/24 Valid Nonecovered by 38.22.178.0/23 666 99% 67
38.22.179.0/24 Valid Nonecovered by 38.22.178.0/23 666 99% 67
2806:490:1000::/48 Valid Nonecovered by 2806:490::/32 629 99% 67
2806:490::/32 Valid RIR databaseLACNIC 631 100% 67

AS-SET

AS275559 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 6 are in fix.csv.

  • ROA: origin1
  • Route object: none4
  • Route object: not announced1
ChangePrefix or setDetailFull-table peers
ROA: origin2806:20d:2d3a::/48ROAs covering it name AS32098, not AS275559. If AS275559 should announce it, add a ROA for AS275559.39 of 633
Route object: none2806:20d:2d3a::/48No route object for it. Add a route object with origin AS275559 in the RIR database for the space.39 of 633
Route object: none38.22.178.0/24No route object for it. A route object for 38.22.178.0/23 with origin AS275559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275559 in the RIR database for the space.666 of 672
Route object: none38.22.179.0/24No route object for it. A route object for 38.22.178.0/23 with origin AS275559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275559 in the RIR database for the space.666 of 672
Route object: none2806:490:1000::/48No route object for it. A route object for 2806:490::/32 with origin AS275559 covers it (filters allowing more-specifics accept it). Add a route object with origin AS275559 in the RIR database for the space.629 of 633

Route objects not announced

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

38.22.178.0/23ARINValid

Routes: the 08:00 UTC snapshots of 2026-11-19 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.