bgpreport

Network · data from 2026-11-12

AS327786 4G Telecom

Registry name: 4G Telecom - 4G Telecom, SS · PeeringDB

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

Announced routes

Every prefix a peer of the route collectors sees with origin AS327786, 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.
38.43.72.0/24 Valid Nonecovered by 38.43.72.0/22 670 100% 66
38.43.74.0/24 Valid Nonecovered by 38.43.72.0/22 670 100% 67
2c0f:6740::/32 Valid None 635 100% 67
38.43.75.0/24 Valid Other IRR onlyRADB 669 99% 68
169.255.26.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 672 100% 66
38.43.72.0/22 Valid RIR databaseARIN 670 100% 68
169.255.24.0/22 Valid RIR databaseAFRINIC, RADB, RIPE-NONAUTH 670 100% 68
169.255.24.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
169.255.25.0/24 Valid RIR databaseAFRINIC, RIPE-NONAUTH 669 99% 68
169.255.27.0/24 Valid RIR databaseAFRINIC, RADB, RIPE-NONAUTH 2 0%low visibility 2

AS-SET

PeeringDB's irr_as_set for AS327786: AS-4GTELECOM. 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 (AS327786 isn't in the set, or no route object for AS327786 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 objectsAS327786 in itNot covered
AS-4GTELECOM AFRINIC 4146 Yes 1

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.

  • Route object: none3
  • Route object: RIR1
ChangePrefix or setDetailFull-table peers
Route object: none38.43.72.0/24No route object for it. A route object for 38.43.72.0/22 with origin AS327786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327786 in the RIR database for the space.670 of 673
Route object: none38.43.74.0/24No route object for it. A route object for 38.43.72.0/22 with origin AS327786 covers it (filters allowing more-specifics accept it). Add a route object with origin AS327786 in the RIR database for the space.670 of 673
Route object: none2c0f:6740::/32No route object for it. Add a route object with origin AS327786 in the RIR database for the space.635 of 636
Route object: RIR38.43.75.0/24Route object only in RADB. Add it in the RIR database for the space.669 of 673

Route objects not announced

Every route object with origin AS327786 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.