bgpreport

Network · data from 2026-11-12

AS270727 MLG. TELECOM

Registry name: AS270727 - Web Connect, BR · PeeringDB

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

Announced routes

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

177.221.129.0/24 No ROA Nonecovered by 177.221.128.0/23 0 0%low visibility 1
177.221.128.0/22 No ROA Other IRR onlyRADB 671 100% 66
177.221.128.0/23 No ROA Other IRR onlyRADB 671 100% 66
177.221.130.0/23 No ROA Other IRR onlyRADB 669 99% 66
2804:7070::/32 No ROA Other IRR onlyRADB 635 100% 69
2804:7070::/33 No ROA Other IRR onlyRADB 635 100% 69
2804:7070:8000::/33 No ROA Other IRR onlyRADB 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS270727: AS-270727. 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 (AS270727 isn't in the set, or no route object for AS270727 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 objectsAS270727 in itNot covered
AS-270727 In no IRR database read today.

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

  • ROA: none7
  • Route object: none1
  • Route object: RIR6
  • AS-SET: not found1
ChangePrefix or setDetailFull-table peers
ROA: none177.221.129.0/24No ROA covers it. Add a ROA for AS270727, maxLength 24.0 of 673
Route object: none177.221.129.0/24No route object for it. A route object for 177.221.128.0/23 with origin AS270727 covers it (filters allowing more-specifics accept it). Add a route object with origin AS270727 in the RIR database for the space.0 of 673
ROA: none177.221.128.0/22No ROA covers it. Add a ROA for AS270727, maxLength 22.671 of 673
Route object: RIR177.221.128.0/22Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.221.128.0/23No ROA covers it. Add a ROA for AS270727, maxLength 23.671 of 673
Route object: RIR177.221.128.0/23Route object only in RADB. Add it in the RIR database for the space.671 of 673
ROA: none177.221.130.0/23No ROA covers it. Add a ROA for AS270727, maxLength 23.669 of 673
Route object: RIR177.221.130.0/23Route object only in RADB. Add it in the RIR database for the space.669 of 673
ROA: none2804:7070::/32No ROA covers it. Add a ROA for AS270727, maxLength 32.635 of 636
Route object: RIR2804:7070::/32Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:7070::/33No ROA covers it. Add a ROA for AS270727, maxLength 33.635 of 636
Route object: RIR2804:7070::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
ROA: none2804:7070:8000::/33No ROA covers it. Add a ROA for AS270727, maxLength 33.635 of 636
Route object: RIR2804:7070:8000::/33Route object only in RADB. Add it in the RIR database for the space.635 of 636
AS-SET: not foundAS-270727PeeringDB names AS-270727; no IRR database read has it.

Route objects not announced

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