bgpreport

Network · data from 2026-11-12

AS28140 Maxiweb Internet Provider

Registry name: AS28140 - G2G INTERNET E SERVICOS DE TELECOM LTDA, BR · PeeringDB

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

Announced routes

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

187.103.216.0/22 Valid Nonecovered by 187.103.216.0/21 672 100% 67
187.103.216.0/24 Valid Nonecovered by 187.103.216.0/21 671 100% 67
187.103.217.0/24 Valid Nonecovered by 187.103.216.0/21 671 100% 67
187.103.218.0/24 Valid Nonecovered by 187.103.216.0/21 671 100% 67
187.103.219.0/24 Valid Nonecovered by 187.103.216.0/21 671 100% 67
187.49.32.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.33.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.34.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.35.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.36.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.37.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.38.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.39.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.40.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.41.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.42.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.43.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.44.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.45.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.46.0/24 Valid Other IRR onlyTC 671 100% 67
187.49.47.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.208.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.209.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.210.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.211.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.212.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.213.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.214.0/24 Valid Other IRR onlyTC 671 100% 67
187.103.215.0/24 Valid Other IRR onlyTC 671 100% 67
2804:1a4::/32 Valid Other IRR onlyRADB, RIPE-NONAUTH, TC 635 100% 69
2804:1a4::/33 Valid Other IRR onlyALTDB, RIPE-NONAUTH 635 100% 69
2804:1a4:8000::/33 Valid Other IRR onlyALTDB, RIPE-NONAUTH 635 100% 69

AS-SET

PeeringDB's irr_as_set for AS28140: TC::AS28140. 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 (AS28140 isn't in the set, or no route object for AS28140 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 objectsAS28140 in itNot covered
TC::AS28140 A single AS number, not a set: AS28140 (this network), 31 route objects.

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

  • Route object: none5
  • Route object: RIR27
  • Route object: not announced4
ChangePrefix or setDetailFull-table peers
Route object: none187.103.216.0/22No route object for it. A route object for 187.103.216.0/21 with origin AS28140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28140 in the RIR database for the space.672 of 673
Route object: none187.103.216.0/24No route object for it. A route object for 187.103.216.0/21 with origin AS28140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28140 in the RIR database for the space.671 of 673
Route object: none187.103.217.0/24No route object for it. A route object for 187.103.216.0/21 with origin AS28140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28140 in the RIR database for the space.671 of 673
Route object: none187.103.218.0/24No route object for it. A route object for 187.103.216.0/21 with origin AS28140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28140 in the RIR database for the space.671 of 673
Route object: none187.103.219.0/24No route object for it. A route object for 187.103.216.0/21 with origin AS28140 covers it (filters allowing more-specifics accept it). Add a route object with origin AS28140 in the RIR database for the space.671 of 673
Route object: RIR187.49.32.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.33.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.34.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.35.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.36.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.37.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.38.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.39.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.40.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.41.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.42.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.43.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.44.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.45.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.46.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.49.47.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.208.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.209.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.210.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.211.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.212.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.213.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.214.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR187.103.215.0/24Route object only in TC. Add it in the RIR database for the space.671 of 673
Route object: RIR2804:1a4::/32Route object only in RADB, RIPE-NONAUTH, TC. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1a4::/33Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.635 of 636
Route object: RIR2804:1a4:8000::/33Route object only in ALTDB, RIPE-NONAUTH. Add it in the RIR database for the space.635 of 636

Route objects not announced

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

187.49.32.0/20RADBNo ROA
187.49.40.0/21ALTDBNo ROA
187.103.208.0/20RADBNo ROA
187.103.216.0/21ALTDBNo 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.