bgpreport

Network · data from 2026-11-12

AS49037 PG-19

Registry name: A1-TELECOM A1 TELECOM LLC, AM · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS49037, 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.
93.185.152.0/24 Valid RIR databaseRIPE 672 100% 66
2a00:8740:2100::/40 Valid RIR databaseRIPE 633 100% 69

AS-SET

PeeringDB's irr_as_set for AS49037: AS-PG19. Expanded from the day's IRR dumps the way bgpq4 does against whois.radb.net: a name with a database is read from that database only, one without from the first database in RADB's order. "Not covered" = this network's own routes that a filter built from the set would leave out (AS49037 isn't in the set, or no route object for AS49037 covers the route; more-specifics of a route object are accepted down to /24 and /48, as with bgpq4 -A -R 24 / -R 48). Customers' routes aren't counted: the collectors show each route's origin, not which network it came through.

NameDatabaseASNsSets Route objectsAS49037 in itNot covered
AS-PG19 RIPE 3145 No 2

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

  • AS-SET: own ASN1
  • Route object: not announced2
ChangePrefix or setDetailFull-table peers
AS-SET: own ASNAS-PG19AS49037 isn't in AS-PG19 (RIPE) once expanded. Add AS49037 to it.

Route objects not announced

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

93.185.153.0/24RIPEValid
2a00:8740:2200::/40RIPEValid

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.